Kubernetes in Highly Restrictive Environments
summary
Shows how to run Kubernetes under strict enterprise controls by wiring audit, authentication and authorization into an identity broker and a central registry, and by enforcing image scanning and approval workflows with Nexus and Aqua. Describes limitations of bare‑metal and vSphere API integrations, achieves HA and disaster recovery with a control‑plane distributor that can recreate clusters from scratch offline, and centralizes metrics via a Prometheus proxy and logs with an ELK stack; solutions work but require heavy ops and storage tradeoffs.
AI-written summary · about
chapters (10)
- 0:00Kubernetes in restrictive envs
- 2:11Restrictive infrastructure challenges
- 6:02Enterprise complexity & legacy
- 10:12Kubernetes for enterprise needs
- 15:15Platform abstraction & services
- 17:24Enterprise Kubernetes architecture
- 24:03Air-gapped cluster deployment
- 26:41Security in restricted setups
- 30:13Centralized monitoring & logs
- 31:59Summary & Q&A
related talks
53mFlying Above the Clouds: Securing Kubernetes
41mKubernetes Security Jumpstart
22mSecuring Kubernetes
34mKubernetes Security 101: Best Practices to Secure Your Cluster
59mKubernetes - going beyond the basics
28mKubernetes Security Low-Hanging Fruit
46mContinuous Kubernetes Security
34mKubernetes Hardening for Regulatory Compliance: A Practical Approach