You may have seen that Alexis Richardson mentioned that we're going to be talking about "config as data" at Kubecon (link to the talk below). What is Configuration as Data? Why would anyone want to use that approach to manage configuration? I wrote a brief post to explain it: https://lnkd.in/gS9dF-iz If you already use the rendered manifest pattern, you're partway there, but still tethered to templates and/or patches. The talk: https://lnkd.in/gE6XBSnt #Kubernetes #GitOps #InfrastructureAsCode
Brian Grant, config as data eliminates template drift, but most teams underestimate the validation complexity. We've seen 40% fewer config errors when teams implement strict schema validation upfront rather than catching issues in CI/CD. What's your strategy for preventing invalid config from reaching production without slowing deployment velocity?
I went through your article sometime ago and have been waiting to see how ConfigHub can solve the configuration complexities ever since. It's a common requirement that extends beyond Kubernetes. Data engineers use metadata-driven processing frameworks to deal with 100s of tables. I wonder if confighub can be used as a generic configuration management solution or purely K8S-centric.