Improve the kubelet check error reporting in the output of agent status
#7495
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?
In combination with DataDog/datadog-agent#6315 , this change improves the
kubelet
check error reported in the output ofagent status
when the agent cannot properly connect to the kubelet.Motivation
In case the agent cannot properly connect to the kubelet, the useful details were in the logs but the output of the
agent status
command gave no clue about the reasons.Here is an example of the
agent status
output in such a case:Here is what the output becomes with this PR:
Additional Notes
This would help the investigation of issues like #2582.
Review checklist (to be filled by reviewers)
changelog/
andintegration/
labels attached