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 Nov 15, 2022. It is now read-only.
Right now pod spec allows you to do both livenessProbe and readinessProbe and since both the fields represent the same data strcuture behind the scene which is called probes.
So essentially you just specify health field which is probe type and then it is populated into readinessProbe and livenessProbe in the output. But if user provides the fields readinessProbe or livenessProbe explicitly then health field is ignored! Those fields are used directly.
The text was updated successfully, but these errors were encountered:
Right now pod spec allows you to do both
livenessProbe
andreadinessProbe
and since both the fields represent the same data strcuture behind the scene which is calledprobes
.So a container will look like the following:
the pod that is generated out of this will look like this:
So essentially you just specify
health
field which isprobe
type and then it is populated intoreadinessProbe
andlivenessProbe
in the output. But if user provides the fieldsreadinessProbe
orlivenessProbe
explicitly thenhealth
field is ignored! Those fields are used directly.The text was updated successfully, but these errors were encountered: