You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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:
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
The text was updated successfully, but these errors were encountered: