-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Application stuck in Progressing status #17208
Comments
If you deploy to https://kubernetes.default.svc |
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. |
With upgrade to 2.11.0, it's now stuck in Degraded instead of Progressing.
|
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
The text was updated successfully, but these errors were encountered: