k8s-controller-reconcile

What problem does it solve?

Kubernetes controller development often suffers from non-idempotent behavior, brittle error handling, and inconsistent state management across resource events. This Skill provides proven patterns to build controllers that reconcile desired and actual state deterministically.

Core Features & Use Cases

• Level-triggered reconciliation that derives desired state from the current world state to avoid missed or duplicate work.
• Reconciler architectures: per-CRD controllers for isolation or mega-reconcilers when cross-resource translation is required.
• Robust event handling, watches, and field index lookups to propagate changes efficiently.
• Clear status management and ownership semantics to enable reliable lifecycle and garbage collection.
• Structured logging and event recording to aid debugging and operator observability.

Quick Start

Set up a reconciler with SetupWithManager, define For/Owns watches, and implement a level-triggered Reconcile that derives the desired state from the current object.