Skip to content

Conversation

glasser
Copy link

@glasser glasser commented May 10, 2024

Since #136 we've had the policy that an OnDelete statefulset is healthy as long as the statefulset spec is updated and the right number of pods are running, even if some of the pods are old and haven't been deleted yet. That's reasonable, but it still can be helpful to be able to see directly in the health message (and eg, in the ArgoCD UI) how many replicas have been updated. This adds that to the message.

…ealth message

Since argoproj#136 we've had the policy that an OnDelete statefulset is healthy as long as the statefulset spec is updated and the right number of pods are running, even if some of the pods are old and haven't been deleted yet. That's reasonable, but it still can be helpful to be able to see directly in the health message (and eg, in the ArgoCD UI) how many replicas have been updated. This adds that to the message.

Signed-off-by: David Glasser <[email protected]>
Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@thiagowfx
Copy link

This is a good UI improvement.

@zygen
Copy link

zygen commented Oct 29, 2024

This would be really helpful!

@glasser
Copy link
Author

glasser commented Nov 22, 2024

I still think this would be a nice improvement, but my team has finally upgraded our ancient StatefulSets to use RollingUpdate like has been the default since 2017.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants