Sources & further reading

References

The documentation, security guidance and background material behind each shared risk and hardening technique covered in the talk.

Shared risks

Every tenant talks to the same API server, and it hosts cluster-scoped machinery they all share.

Highly privileged operators and node-wide DaemonSets are confused deputies waiting to be abused.

RBAC complexities can make Multi-Tenancy a lot harder.

One flat LAN by default — and the API server turns tenant-to-tenant reachability into SSRF by design.

Tenants share the node and its kernel — so a container breakout puts every workload on that node at risk.

One shared registry means one poisoned push can reach every tenant that pulls the image.

Place tenants on dedicated groups of nodes to remove the shared kernel and reduce the blast radius of a node compromise.