Operators and CRDs
Extending the API with your own types: CustomResourceDefinitions, controllers that reconcile them, admission webhooks that intercept writes, and operators encoding day-2 ops. Interviewers probe it to see if you treat Kubernetes as an extensible control plane.
part ofKubernetesoverview, primer and where to startread it →on this pageshowhide
explore
- CustomResourceDefinitions6 questions
- Custom Controllers and Reconcile Loops5 questions
- The Operator Pattern4 questions
- Admission Webhooks5 questions
- CRD Versions & Conversion4 questions
- Status & Scale Subresources3 questions
- controller-runtime & Kubebuilder4 questions
questions
page 2 of 2You are standardizing a platform where 40 teams want managed databases, caches and queues via Kubernetes Operators across a fleet of shared clusters. How do you decide the scoping, permissions and upgrade strategy for those operators?
level: principalimportance: nice to knowfreq 30%
basics
~20 sCurate a small vetted set of operators; decide per operator whether it runs namespaced or cluster-wide, grant the narrowest RBAC that works, and treat its CRDs as a cluster-wide singleton API needing versioned, staged upgrades. Monitor operators as tier-1 services and define who is on call for them.
showing 31–31 of 31