Closed hflobao closed 3 weeks ago
@hflobao I think your spec.forProvider.accessConfig
block is incorrect. Rather than two objects in an array, it should be a single array with one object like this:
spec:
deletionPolicy: Delete
forProvider:
accessConfig:
- authenticationMode: CONFIG_MAP
bootstrapClusterCreatorAdminPermissions: true
Hi @mattfield, thanks for taking time to answer! You're right! It's provisioning properly now. Thanks a lot!
Is there an existing issue for this?
Affected Resource(s)
Resource MRs required to reproduce the bug
Steps to Reproduce
Try to provision an EKS cluster with the "accessConfig" specified in the MR as per the documentation for the v1.5.0:
https://marketplace.upbound.io/providers/upbound/provider-aws-eks/v1.5.0/resources/eks.aws.upbound.io/Cluster/v1beta1#doc:spec-forProvider-accessConfig
What happened?
When trying to provision using the "accessConfig", the behavior is as if the bootstrapClusterCreatorAdminPermissions is set to false, even if I omit the parameter to use the default value or if I explicitly specify it with the value of true.
If the authenticationMode is set to "API" or "API_AND_CONFIG_MAP", the cluster get created, but with the value of false in the bootstrapClusterCreatorAdminPermissions. If the authenticationMode is set to "CONFIG_MAP", I get an error and the cluster is not created, as it requires the bootstrapClusterCreatorAdminPermissions to be set to true.
Relevant Error Output Snippet
Crossplane Version
1.16.0
Provider Version
1.5.0
Kubernetes Version
1.29
Kubernetes Distribution
EKS
Additional Info
No response