Replies: 1 comment
-
Seeing strange behaviour where it will trigger the reconcile and work as I would have expected but not immediately |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
My controller owns and is responsible for making a deployment. The one container in this deployment has a liveness and startup probe. When the probes reach their failure threshold kubelet restarts the container. On this event when kubelet restarts the container I'd like to receive a reconcile to retrieve the latest container status (which I am currently not).
My understanding was that because my controller
Owns(&corev1.Pod{})
(and the pod has the correct owner refs), that the update event on the pod triggered by kubelet ofWarning Unhealthy 4m17s (x45 over 39m) kubelet Liveness probe failed: HTTP probe failed with statuscode: 503
would cause a reconcile. Is there something I am missing?Manager setup:
Beta Was this translation helpful? Give feedback.
All reactions