Replies: 1 comment 4 replies
|
I do not see any conflict in the expressions. So not sure what exactly is the problem Karpenter has. In any case, Strimzi does not set any affinity since Strimzi 0.49.0. You do not list your Strimzi version nor share any logs and other proper information. But you should probably upgrade. |
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Description:
Our Karpenter deployment (v1.5.0) is unable to reconcile the nodeAffinity rules for KafkaNodePools due to conflicting keys inside the matchExpressions array of the generated Pod spec.
Context:
nodeSelectorTermsin our KafkaNodePool configurationObserved Behaviour:
Karpenter (v1.5.0) fails to evaluate or satisfy these criteria because the combination of our explicit node requirements and Strimzi's Exists operator creates a conflicting or unresolvable constraint within a single evaluation block. As a result, Karpenter's controller cannot resolve the expression into a valid NodePool provisioning request.
Temporary Workaround
Replaced the conflicting
topology.kubernetes.io/zonekey withtopology.k8s.aws/zone-idso the keys do not collide.Advise please
Would it be possible to have strimzi-operator add the extra expression only if another expression with the same key does not already exist?
All reactions