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
Using a static tool like kube-score throws this error:
apps/v1/Deployment prometheus-msteams in my-namespace 💥
[CRITICAL] Pod Probes
· Container has the same readiness and liveness probe
Using the same probe for liveness and readiness is very likely
dangerous. Generally it's better to avoid the livenessProbe than
re-using the readinessProbe.
More information: https://github.com/zegl/kube-score/blob/master/README_PROBES.md
Describe the bug
Right now the deployment yaml (from the helm chart) has the same liveness and readiness probe:
Using a static tool like kube-score throws this error:
Version
To Reproduce
Use the manifest generated by latest helm chart and pass it to
kube-score
will result in such an error pasted above.Expected behavior
Liveness probe and readiness probe should be different. There are some recommendations here: https://github.com/zegl/kube-score/blob/master/README_PROBES.md#livenessprobe
Additional context
No additional context, but can provide if something is required.
The text was updated successfully, but these errors were encountered: