You need to add a liveness and readiness probe to query each container, if the probe fails, the entire pod will be restarted .
Add liveness object that calls any API that returns 200 to you from another container and both liveness and readiness probes run in infinite loops.
For example, If X depended to Y So add liveness in X that check the health of Y.
Both readiness/liveness probes always have to run after the container has been started .
kubelet component performs the liveness/readiness checks and set initialDelaySeconds and it can be anything from a few seconds to a few minutes depending on app start time.
Below is the configuration spec
You get this error when your pod ...READ MORE
Pending pod cannot be scheduled onto a ...READ MORE
By default, anti-affinity is not attempted by ...READ MORE
By declaring pods with the label(s) and ...READ MORE
Hey @nmentityvibes, you seem to be using ...READ MORE
Try using ingress itself in this manner
except ...READ MORE
Hi Kalgi after following above steps it ...READ MORE
Follow these steps:
$ kubeadm reset
$ kubeadm init ...READ MORE
One way is Init Containers.
These are for ...READ MORE
By default, anti-affinity is not attempted by Kubernetes as ...READ MORE