Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: ClusterAuth controller doesn't inherit the feature settings #1438

Open
1 task done
r-nasiri opened this issue Aug 2, 2024 · 1 comment
Open
1 task done
Labels
bug Something isn't working needs:triage stale

Comments

@r-nasiri
Copy link

r-nasiri commented Aug 2, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Affected Resource(s)

eks.aws.upbound.io/v1beta1 - ClusterAuth

Resource MRs required to reproduce the bug


apiVersion: eks.aws.upbound.io/v1beta1
kind: ClusterAuth
metadata:
  name: my-cluster-auth
spec:
  forProvider:
    clusterNameSelector:
      matchLabels:
        testing.upbound.io/example-name: example-clusterauth
    region: us-west-1
  managementPolicies:
  - Create
  - Observe
  - LateInitialize

Steps to Reproduce

  1. Create the ClusterAuth resource without the managementPolicies set
  2. Make sure the ClusterAuth is created successfully.
  3. Add the managementPolicies to ClusterAuth resource
  4. the resource is not reconciled and generates error

What happened?

all other resources in eks.aws.upbound.io provider allow setting the managementPolicies but ClusterAuth controller generates an error.

Relevant Error Output Snippet

spec.managementPolicies is set to a non-default value but the feature is not enabled: [Create LateInitialize Observe]

Crossplane Version

1.16.0

Provider Version

1.10.0

Kubernetes Version

1.29

Kubernetes Distribution

EKS

Additional Info

No response

@r-nasiri r-nasiri added bug Something isn't working needs:triage labels Aug 2, 2024
Copy link

github-actions bot commented Nov 1, 2024

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

@github-actions github-actions bot added the stale label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs:triage stale
Projects
None yet
Development

No branches or pull requests

1 participant