-
Couldn't load subscription status.
- Fork 198
fix: take into account units state on liveness #10060
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
fix: take into account units state on liveness #10060
Conversation
| Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
35af5b5 to 315fb34 Compare 9ad3648 to 94ba13c Compare |
💛 Build succeeded, but was flaky
Failed CI StepsHistory
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for cleaning up the loop. Looks good.
| @Mergifyio backport 8.18 8.19 9.0 9.1 |
✅ Backports have been created
|
* fix: take into account units state on liveness * extract check components state to helper * merge conditional assignment into variable declaration (cherry picked from commit 4b818a1)
* fix: take into account units state on liveness * extract check components state to helper * merge conditional assignment into variable declaration (cherry picked from commit 4b818a1)
* fix: take into account units state on liveness * extract check components state to helper * merge conditional assignment into variable declaration (cherry picked from commit 4b818a1)
* fix: take into account units state on liveness * extract check components state to helper * merge conditional assignment into variable declaration (cherry picked from commit 4b818a1)
* fix: take into account units state on liveness * extract check components state to helper * merge conditional assignment into variable declaration (cherry picked from commit 4b818a1)
* fix: take into account units state on liveness * extract check components state to helper * merge conditional assignment into variable declaration (cherry picked from commit 4b818a1)
* fix: take into account units state on liveness * extract check components state to helper * merge conditional assignment into variable declaration (cherry picked from commit 4b818a1) Co-authored-by: Ruben Ruiz de Gauna <rubenruizdegauna@proton.me>
* fix: take into account units state on liveness * extract check components state to helper * merge conditional assignment into variable declaration (cherry picked from commit 4b818a1)
* fix: take into account units state on liveness * extract check components state to helper * merge conditional assignment into variable declaration (cherry picked from commit 4b818a1) Co-authored-by: Ruben Ruiz de Gauna <rubenruizdegauna@proton.me>
* fix: take into account units state on liveness * extract check components state to helper * merge conditional assignment into variable declaration (cherry picked from commit 4b818a1) Co-authored-by: Ruben Ruiz de Gauna <rubenruizdegauna@proton.me>
* fix: take into account units state on liveness * extract check components state to helper * merge conditional assignment into variable declaration (cherry picked from commit 4b818a1) Co-authored-by: Ruben Ruiz de Gauna <rubenruizdegauna@proton.me>
* fix: take into account units state on liveness * extract check components state to helper * merge conditional assignment into variable declaration




What does this PR do?
This PR adds the check of the component's unit's state on liveness endpoint. If a component state is healthy, but a unit state is degraded or failed, the liveness endpoint will return a 500.
Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
Liveness probes will now fail if a component state is healthy but any of the units is failed or degraded, likely causing the container to be restarted (see https://kubernetes.io/docs/concepts/configuration/liveness-readiness-startup-probes/#liveness-probe).
Related issues