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
{{ message }}
This repository has been archived by the owner on Aug 31, 2022. It is now read-only.
It's a good idea. However, testing whether it can connect to the API is not a good probe. If it cannot, it should be in crash-loop. However, readiness can be set after the pod performs the watch call to API. Watch is called once, then for labels, we get the objects. For clusters, that might not grant "read" permissions for all types (CRDs are not included by default) we ignore the error. So it gets trickier. What can be the solution?
It would be awesome if there were endpoints for health / liveness probes defined, (e.g. test if it can connect to k8s API) https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
The text was updated successfully, but these errors were encountered: