-
Notifications
You must be signed in to change notification settings - Fork 12
Common issues and solutions
Zachary Seguin edited this page Jul 15, 2020
·
13 revisions
Here's some of the common issues and resolutions that have been encountered in the environment.
If gatekeeper has crashed, it will begin to block commands that require further validation. Unfortunately, due to a bug, gatekeeper will not restart on its own and requires manual intervention.
kubectl patch validatingwebhookconfigurations.admissionregistration.k8s.io gatekeeper-validating-webhook-configuration --type=json -p='[{"op":"replace","path":"/webhooks/0/failurePolicy","value":"Ignore"}]'
Once gatekeeper is running (1/1), run the following to restore the failure policy:
kubectl patch validatingwebhookconfigurations.admissionregistration.k8s.io gatekeeper-validating-webhook-configuration --type=json -p='[{"op":"replace","path":"/webhooks/0/failurePolicy","value":"Fail"}]'