Kubernetes Policy WG Intro
summary
Working group forms in February 2018 with weekly meetings and contributors from Google, Huawei, IBM and Red Hat and defines three use cases—compliance/data tagging, dynamic capacity/quota, and cluster security lifecycle—plus three concrete proposals: scheduling policy (namespace-based scheduler and priority controls slated for implementation across the next two releases), service topology routing rules to favor locality, and security profile policy (namespace templates, pod/network/pod-security aggregation). Prototypes and integrations mentioned include OPA, SPIFFE, and kube-arbitrator with live demos planned.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 7:37Use Cases
- 15:13Proposals
- 15:28Scheduling Policy
- 18:21Policy Guidelines
- 21:32Security Profile Policy
- 23:13Other Possibilities
- 26:11Second Cycle Planning
- 27:23Community Collaboration
- 29:38Deep Dive Session
- 30:34Slides
related talks
36mKubernetes Policy, Governance, And Compliance: A WG Policy Update
16mDeep Dive: Kubernetes Policy WG
26mIntro + Deep Dive: Kubernetes Policy WG
20mDeep Dive: Kubernetes Policy WG
27mPolicy Matters! The Why, What, and How of Kubernetes Policy Management
40mKubernetes Networking Panel: Collaborate on the Spec, Compete on Execution
35mDeep Dive: Kubernetes Working Group for Multi-tenancy
36mKubernetes Security After Pod Security Policies Removal