OpenShell Kubernetes Operator

github.com

13 pointsxfiler2 comments

Being in Kubecon this week and now this project, I'm a bit surprised at how heavily some people lean into Operators. I've always been hesitant to deploy operators into my clusters unless they provide a significant advantage compared to just using argocd just because of how heavily they can hit the k8s API. Not sure if anyone has run into the same issues?

Doesn't it depend on how widely and how many things an operator subscribes to?

I'm pretty invested in vault-secrets-operator and vault-config-operator.

Simply because of the amount of custom scripting I don't have to do.

But I have thought: I wonder if one operator could do the job.

Looking at vault, VSO and VCO codebases, you get a little daunted. There's a lot of code.

Reply on news.ycombinator.com