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

Nodegroup taints are not getting applied or removed #2128

Open
IonitaCatalin opened this issue Nov 25, 2024 · 0 comments
Open

Nodegroup taints are not getting applied or removed #2128

IonitaCatalin opened this issue Nov 25, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@IonitaCatalin
Copy link

What happened?

We have an entire EKS cluster created via a Composition. This composition creates a specialised nodegroup which is meant to run Karpenter controller's replicas, this nodegroup was supposed to be tainted but due to an error the nodegroup was not tainted when creating.
In an attempt to fix this issue we created a new version of the composition in which the nodegroup has the taints like so:

 spec:
   forProvider:   
      taints:
        - effect: NO_SCHEDULE
          key: karpenter
          value: owned

This applied the taints for the cluster-local nodegroup.eks.aws.crossplane.io but the cloud counterpart was not updated accordingly.

How can we reproduce it?

Create a new nodegroup, and try to taint it post creation. The new taints are not applied.

What environment did it happen in?

Crossplane version: 1.16.2
provider-aws version: 0.48.1
Kubernetes version: 1.31.2

@IonitaCatalin IonitaCatalin added the bug Something isn't working label Nov 25, 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
Projects
None yet
Development

No branches or pull requests

1 participant