We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Kubernetes documentation states that readiness probes are not supported on initContainers:
https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
Also, Init Containers do not support readiness probes because they must run to completion before the Pod can be ready.
Based on this, I think that lack of a readiness probe should be ignored for initContainers. This would bring my cluster's score up a bit. 😃
The text was updated successfully, but these errors were encountered:
Great catch, thanks! We'll work on fixing that.
Sorry, something went wrong.
ensuring that readiness probes in init containers are not validated to …
b1e9559
…fix #112
f5c7087
Successfully merging a pull request may close this issue.
The Kubernetes documentation states that readiness probes are not supported on initContainers:
https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
Based on this, I think that lack of a readiness probe should be ignored for initContainers. This would bring my cluster's score up a bit. 😃
The text was updated successfully, but these errors were encountered: