Open burner1024 opened 9 months ago
If you deploy to https://kubernetes.default.svc it may be related to https://github.com/argoproj/argo-cd/issues/17016 The workaround solved it for me.
My argo is 2.9 and there's a dozen of other applications that don't exibit this issue, so doesn't look that way.
status:
availableReplicas: 2
conditions:
- lastTransitionTime: "2024-02-14T12:52:24Z"
lastUpdateTime: "2024-02-14T12:52:24Z"
message: Deployment has minimum availability.
reason: MinimumReplicasAvailable
status: "True"
type: Available
- lastTransitionTime: "2024-02-14T12:52:13Z"
lastUpdateTime: "2024-02-14T12:52:24Z"
message: ReplicaSet "karpenter-root-648b85ffcc" has successfully progressed.
reason: NewReplicaSetAvailable
status: "True"
type: Progressing
observedGeneration: 1
readyReplicas: 2
replicas: 2
updatedReplicas: 2
I kinda suspect it's due to order of conditions. In other, "healthy" deployments in the cluster, I see "Progressing" as the first item, and "Available" second. No idea how to rearrange them though, seems to be managed by k8s itself, changes just get reverted. And re-creating keeps the same order.
With upgrade to 2.11.0, it's now stuck in Degraded instead of Progressing.
...
26m Normal ResourceUpdated application/karpenter-root Updated health status: Degraded -> Healthy
26m Normal ResourceUpdated application/karpenter-root Updated health status: Degraded -> Healthy
23m Normal ResourceUpdated application/karpenter-root Updated health status: Degraded -> Healthy
21m Normal ResourceUpdated application/karpenter-root Updated health status: Degraded -> Healthy
20m Normal ResourceUpdated application/karpenter-root Updated health status: Degraded -> Healthy
17m Normal ResourceUpdated application/karpenter-root Updated health status: Degraded -> Healthy
16m Normal ResourceUpdated application/karpenter-root Updated health status: Degraded -> Healthy
14m Normal ResourceUpdated application/karpenter-root Updated health status: Degraded -> Healthy
11m Normal ResourceUpdated application/karpenter-root Updated health status: Degraded -> Healthy
11m Normal ResourceUpdated application/karpenter-root Updated health status: Degraded -> Healthy
8m36s Normal ResourceUpdated application/karpenter-root Updated health status: Degraded -> Healthy
5m58s Normal ResourceUpdated application/karpenter-root Updated health status: Degraded -> Healthy
5m36s Normal ResourceUpdated application/karpenter-root Updated health status: Degraded -> Healthy
2m36s Normal ResourceUpdated application/karpenter-root Updated health status: Degraded -> Healthy
52s Normal ResourceUpdated application/karpenter-root Updated health status: Degraded -> Healthy
Checklist:
argocd version
.Describe the bug
Deployment stuck in Progressing state, with "HEALTH DETAILS Waiting for rollout to finish: 0 of 2 updated replicas are available..."
To Reproduce
Install Karpenter.
Expected behavior
Deployment not stuck.
Screenshots
Version
Logs