[9.0] (backport #9673) Liveness agent state#9957
Merged
Conversation
* fix(tests): update liveness/readiness test cases to assert status code and remove unused vars * fix: correct order of fields in LivenessFailConfig for degraded state * fix: remove unnecessary check for coordinator mode in liveness handler (already handled) * fix: add unhealthy coordinator state handling in liveness handler * add changelog fragment (cherry picked from commit d3b9427)
Contributor
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
nkvoll
approved these changes
Sep 15, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.




What does this PR do?
This PR includes the aggregated status of the agent node to the liveness health check.
As a bonus, it also adds status code assertion to the tests, which were missing before. (All liveness/readiness tests were passing without any assertions).
Why is it important?
Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
Liveness probes will now fail if the configuration is invalid, likely causing the container to be restarted (see https://kubernetes.io/docs/concepts/configuration/liveness-readiness-startup-probes/#liveness-probe).
How to test this PR locally
elastic-agent.ymlfile with an invalid output, i.e setuse_output: nonexistentelastic-agent statusRelated issues
This is an automatic backport of pull request #9673 done by [Mergify](https://mergify.com).