One of the super powers Kubernetes gives us is our ability to expand the API, modeling our architectures and dependencies with CRDs, leveraging Kubernetes as a platform for building platforms. Getting something up and running can take just minutes, but debugging synchronization problems and unexpected behaviors can take days or weeks for folks just starting out. Compound this problem with a lack of advanced controller creation advice, and a lack of direction on the norms and expectations around spec/status and behavior, and it is easy to see how even hardened engineers with years of experience can fail on their first attempts at writing their first Kubernetes based declarative API.

We cover will some common mistakes and mis-understandings around reconciliation, and explain what we can do instead. And look at unspoken norms around API shapes in spec and status, explain why they are useful, and send you on your way with new found confidence to wield the power of a platform developer.