A Deployment, a Service in front of it, and a ConfigMap whose one interesting value is the hostname the Service reports in its status. Kubebuilder turns building the first controller into a pleasant afternoon. The tenth brings its own reconcile bugs, upgrade path, and on-call rotation.
It's slightly different each time, and it exists in thousands of organizations. Every ingredient, no recipe Kubernetes has the ingredients: CRDs define new types. Server-side apply tracks who owns each field.
CEL evaluates expressions, and OpenAPI schemas type every field. What Kubernetes does not provide is the recipe. Nothing says that several resources form one thing, or that a value in one comes from the status of another and must wait for it.
KubeCon + CloudNativeCon is taking place in Salt Lake City from November 9 to 12. Every tool that manages a set of resources builds that piece itself, and keeps adding to it.
