"Musty Bits" McGee<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@seanhood" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>seanhood</span></a></span> there's a few key changes in my design<br>1. A full, functional programming language for inflating configuration into manifest files. We publish a versioned library of this as an OCI artifact, and any resources or changes the library doesn't support yet can be done by passing a closure/function to an escape hatch.<br>2. Kubernetes is THE control plane. Anything that would have been terraform is now Crossplane or ACK or whatever operator. No living in two worlds or picking the best-of-the-worst couplings between TF and K8s <br>3. The control plane desired stare should include any cross-resource dependencies. It's still GitOps but there should be no need for any write back or chore commits. This is where the custom operator comes in, though potentially Kro could work.</p><p><a href="https://eigenmagic.net/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> <a href="https://eigenmagic.net/tags/KubernetesDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>KubernetesDev</span></a> <a href="https://eigenmagic.net/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> <a href="https://eigenmagic.net/tags/k8sDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8sDev</span></a></p>