The safeguards map / 3.7 Admission and owner settings
Capsule
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
A Kubernetes multi-tenancy operator that groups namespaces into tenants and applies tenant-level policies, enforced through admission webhooks.
Where it sits
3.7 Admission and owner settings (primary): Groups namespaces into tenants on a shared Kubernetes cluster and enforces policies the cluster owner defines per tenant through Kubernetes admission control.
Leverage Kubernetes Admission Controllers to enforce the industry security best practices and meet policy requirements.
captured
and other policies defined at the tenant level are automatically inherited by all the namespaces in the tenant
captured
the Capsule Policy Engine keeps the different tenants isolated from each other
captured
Facts
- Concern
- security
- Names the law
- no
- Subject
- software
- Used by
- those who run it
- Runs
- at runtime
- Policy comes from
- owner-entered settings
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.