Hi, Team!
Kubernetes version: Client Version: v1.29.2
Cloud being used: EKS
I got a question related to the nodeAffinity set.
All I want to do is to set my argocd-redis-ha pods to be scheduled with nodeAffinity, but it’s not working as I expected.
All the other pods except for the argocd-redis-ha
are deployed with the nodeAffinity.
I’ve set redis-ha.affinity as follows:
set {
name = "redis-ha.affinity"
value = <<EOF
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: Name
operator: In
values:
- "name-of-node"
topologyKey: "kubernetes.io/hostname"
EOF
}
The following is the Kubernetes events log. There’s no Pod-AntiAffinity configuration I’ve set.
10s (x239 over 19h) Warning FailedScheduling Pod/argocd-redis-ha-haproxy-abc1234d5-efgh6 0/xx nodes are available: xx node(s) had untolerated taint {karpenter.sh/disruption: disrupting}, xx node(s) didn't match Pod's node affinity/selector, xx node(s) didn't match pod anti-affinity rules. preemption: 0/xx nodes are available: xx Preemption is not helpful for scheduling, 2 No preemption victims found for incoming pod.
10s (x239 over 19h) Warning FailedScheduling Pod/argocd-redis-ha-server-0 0/18 nodes are available: xx node(s) had untolerated taint {karpenter.sh/disruption: disrupting}, xx node(s) didn't match Pod's node affinity/selector, xx node(s) didn't match pod anti-affinity rules. preemption: 0/xx nodes are available: xx Preemption is not helpful for scheduling, xx No preemption victims found for incoming pod.
Executing the terraform apply command terminates with a “context deadline exceeded” error message.
A│ Error: client rate limiter Wait returned an error: context deadline exceeded
│ with helm_release.argocd,
│ on eks_helm.tf line 135, in resource “helm_release” “argocd”:
│ 135: resource “helm_release” “argocd” {
Any help would be greatly appreciated!