The safeguards map / 3.7 Admission and owner settings
Kubernetes (admission control)
Drafted with AI
Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made
The admission control stage of the Kubernetes API server, which checks requests against built-in controllers, in-API CEL policies and external admission webhooks before a resource is stored.
Where it sits
3.7 Admission and owner settings (primary): Intercepts each request to the Kubernetes API server before the resource is stored and rejects it when an admission controller, an in-API CEL policy or an external admission webhook fails it.
An admission controller is a piece of code that intercepts requests to the Kubernetes API server prior to persistence of the resource, but after the request is authenticated and authorized.
captured
MutatingAdmissionPolicy and ValidatingAdmissionPolicy provides a way to embed declarative mutation/validation code within the API, without relying on any external HTTP callouts.
captured
Admission webhooks are HTTP callbacks that receive admission requests and do something with them.
captured
Facts
- Concern
- security
- Names the law
- no
- Subject
- software
- Used by
- those who run it
- Runs
- at runtime
- Policy comes from
- owner-entered settingsan external decision point
Handoffs
None recorded. A mapped entry with no handoff is here for its foundation home.
Every quote is verbatim from a stored capture of the page linked under it. Placement is our reading of the product's own documentation; no publisher has reviewed or endorsed it. Rows CC BY 4.0. Names, marks and logos belong to their owners; logos identify each product and are not part of the dataset.