Implementing Anti-patterns: Kubernetes Cross-namespace Resource Ownership
summary
Kubernetes forbids namespace-scoped ownerReferences (warning since v1.20) so a solution creates paired CRDs called meteor and its shadow comma, uses finalizers and status-tracked UID+namespace entries, and an operator written with Operator SDK and Go client libraries to create/delete commas across namespaces. The controller lists external namespaces, creates shadow commas, sets local ownerReferences, and on deletion removes commas and their image streams/pipelines; deployed on the bridge cluster and tested successfully.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:38Kubernetes Concepts
- 3:01Agenda
- 5:57When To Use Namespaces
- 6:39Resource Quota
- 7:53Use Cases of Kubernetes
- 8:56Owners and Dependents
- 11:37Finalizers
- 22:07Finalizer
related talks
35mSharing is Caring: Your Kubernetes Cluster, Namespaces, and You
21mMaking Kubernetes Safer with User Namespaces
29mKubernetes Custom Resources with Kubeless and Metacontroller
38mKubernetes Beyond
40mBootiful Kubernetes Operators
46mOperators Live in the Past: Designing Reliable Kubernetes Controllers
55mIntroduction to Kubernetes Operators
40mExtending K8s- Introducing Custom Resources, Controllers, Operators & Schedulers