Post

Yes! Very much so. It's long story, but the short version to why CUE's been a great fit is that we didn't want to own/build/run controllers/operators at our size (yet), but we also didn't want to use a general purpose programming language or bash or scripting for automation either. 1/4

As a result, CUE has filled a really good in between niche where we've been able to have validations, configs, overlays, etc. without needing an expansive setup with helm charts, various kustomizations, kubeconform, etc. We use ArgoCD for deployment and CUE for everything up until that point. 2/4

Of course, there's still other tooling in the loop. Some small bash shims, for example. However, mainly ArgoCD does the work. CUE gets us the generated manfests that it uses. Some of the ArgoCD Applications from upstream helm sources, but we don't manage or vendor them directly (yet(?)). 3/4