GitOps terminology clarification: Use Git as a Source of Record, and Kubernetes as a Source of Truth. https://www.taos.com/source-of-record-vs-source-of-truth/ …
IMO, apply is a significant innovation in K8s. There should be no hard line between human configuration and automation. Pushing merging into the ecosystem exacerbates tool fragmentation -- been there, done that. The API schema complexity is a bug, though.
-
-
Apply is great. I use and teach it exclusively. But it doesn’t help resolve the multi-master issue.
-
I think the most interesting enhancement would be attribute based custom conflict resolution on resources (similar to how we do validation in CRDs).
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.