Skip to content

Comments

feat: Add dynamic admission controller section to scs 0217#1106

Open
viccuad wants to merge 1 commit intoSovereignCloudStack:mainfrom
viccuad:feat/dyn-adm-controller
Open

feat: Add dynamic admission controller section to scs 0217#1106
viccuad wants to merge 1 commit intoSovereignCloudStack:mainfrom
viccuad:feat/dyn-adm-controller

Conversation

@viccuad
Copy link

@viccuad viccuad commented Feb 18, 2026

Dynamic Admission Controllers from Policy Engines constitute a special attack surface.

From the SIG security threat model, the majority of mitigations are implemented by policy engines and cluster operators.

But cluster providers must enable mutual TLS for secure consumption of Kubernetes API webhooks, and cluster operators must use a policy engine that authenticates against those TLS-terminated webhooks (not all policy engines do).

this, the Kubernetes API server MUST be configured with mutual TLS
authentication for the Webhooks (see [Kubernetes
docs](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/#authenticate-apiservers))
. The Policy Engine MUST be able to authenticate the API server and MUST be
Copy link
Author

@viccuad viccuad Feb 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As an example, here's the threat model for Kubewarden, and the documentation on how to generally configure a cluster API server & Kubewarden, or specifically configure both a K3s API server & Kubewarden as well.

@viccuad viccuad force-pushed the feat/dyn-adm-controller branch 2 times, most recently from 85bfd66 to e4d0aa3 Compare February 18, 2026 10:39
Dynamic Admission Controllers from Policy Engines constitute a special
attack surface.

From the SIG security threat model, the majority of mitigations are
implemented by policy engines and cluster operators.

But cluster providers must enable mutual TLS for secure consumption of
Kubernetes API webhooks, and cluster operators must use a policy engine
that authenticates against those TLS-terminated webhooks (not all policy
engines do).

Signed-off-by: Víctor Cuadrado Juan <vcuadradojuan@suse.de>
@viccuad viccuad force-pushed the feat/dyn-adm-controller branch from e4d0aa3 to f6d3a0d Compare February 18, 2026 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant