You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
The key has expired.
Kuberhealthy 2.3.0
Upgrade Instructions:
When upgrading to this release, you must be sure the khjob custom resource is applied in your cluster. Without this, the check reaper will crash. If you use the Helm chart, this will be done for you automatically.
Features:
Breaking Change: ConfigMap support for Kuberhealthy with live-reloading. #252, #482#557@jdowni000
Make sure the Kuberhealthy configMap is applied and the configMap volume added is added to the Kuberhealthy deployment
Daemonset and Deployment checks now offer nodeSelector options. #546, #547, #549@jonnydawg
Daemonset check now gracefully handles intermittent failures when making kube api calls using exponential backoff. This addresses a bug where daemonset check falsely reports an error when etcd leader changes during ds check run. #527, #515@joshulyne
Fix goroutine leak from kuberhealthy watch events and refactor concurrency on external checks #533, #548@sbueringer@integrii
Fixes a bug where the main kuberhealthy process is blocked if a checker pod gets stuck in "pending" or "container creating". Also ensures that pods that aren't in succeeded or failed phases are evicted properly during cleanup. #447, #540@joshulyne
Fix for misconfigured khchecks that block the main kuberhealthy process by fetching all khchecks using unstructured objects #554#573@joshulyne
Fix scratch image for Kuberhealthy, no longer giving missing /bin/sh error. Also fixed a null pointer error. #632@integrii
Security Context added to check-reaper pods #607@czunker
Fix missing ‘CurrentMaster’ field on Kuberhealthy status page #584@joshulyne