Kubernetes / Cluster Operations, Access & Incident Response
Diagnose an admission webhook timeout before bypassing policy
A create or update can fail because its configured webhook endpoint is unavailable. Inspect the registered configuration and supporting service.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl get validatingwebhookconfigurations
kubectl get mutatingwebhookconfigurationsRead the result
The listings identify registered admission configurations, not which one caused the request failure. The exact error names the relevant webhook and call.
Resolve and verify
Inspect that webhook's intended Service, certificates and controller health through its owner's runbook. Restore the dependency and verify a permitted request.
Before changing production
Do not delete webhook configurations or change failure policy to ignore without an explicit reviewed risk decision.