Revision 4ec2c362484f3f57ecd85e938524eb5cbea656c7 authored by Steven Johnson on 01 April 2023, 15:12:50 UTC, committed by Timo Beckers on 21 June 2023, 08:53:55 UTC
I was looking into kubelet liveness checks returning HTTP 503 response codes recently and noticed that there was not any logging in the agent that indicated the issue.

The logging I'm adding in this PR allowed me to track down why the liveness checks were failing by giving the error message associated with the current subsystem's unhealthy state.

Signed-off-by: Steven Johnson <sjdot@protonmail.com>
1 parent 5a1770c
History

README.md

back to top