kubernetes-operator

Topics in the source

• Kubernetes Operator
• When to use
• When NOT to use
• Core principle: an operator is a reconcile loop, not a script
• Quick start
• The 3 Python tools
• crdvalidator.py
• reconcilelint.py

Build operators that reconcile correctly. Most operator bugs are not Kubernetes bugs — they are reconcile-loop bugs: missing finalizers, blocking calls, no requeue on transient errors, status drift, RBAC over-grants. This skill catches them deterministically before they reach a cluster. Building a new Kubernetes Operator (controller for a CRD) Reviewing an existing operator for capability-level gaps Auditing a CRD spec for status/conditions/finalizer correctness Choosing a framework (controller-runtime / kubebuilder / operator-sdk / metacontroller / KOPF) Designing the API surface of a Custom Resource Hardening RBAC, leader election, or webhook validation Plain Helm chart packaging → use helm-chart-builder Standard kubectl operations / blue-green deploys → use senior-devops General k8s security posture → use cloud-security "I want to run a workload" — that's a Deployment / Job, not an operator Operators that fail are the ones that: 1. Treat reconcile as imperative (do this, then this, then this) instead of declarative (make actual=desired, idempotently) 2. Don't requeue transient failures 3. Don't use finalizers, leaving orphan resources 4. Mutate spec instead of status 5. Don't us

This is an excerpt. Refer to the complete source and its current requirements.