k8s-api-troubleshooting
API server troubleshooting
Find out why the API server refuses or fails a request, and propose a fix. Read first, ask before changing. Run the investigation commands freely. Run a command under an "Ask first" line only after the user approves that exact command; if your credentials do not allow it, give it to the user to run. Never run a "Proposed fix"; hand it to the user.
Every request goes through the same steps in the API server: authentication (who is
asking: a 401 if nobody), authorization (may they: a 403 from RBAC), admission
(mutating webhooks, schema validation, then ValidatingAdmissionPolicies and validating
webhooks), then storage in etcd. Requests for an aggregated API (an APIService
such as v1beta1.metrics.k8s.io) are sent on to another server instead, and
discovery lists every group and version, including those. A failure at any step comes
back to the caller, so the error message usually names the step: the webhook, the
APIService, the kind and version, or the limit.