7 ms·

I'd please ask people to don't write operators unless absolutely necessary. I used a certain tool which had its own config format, and it's "cloudnative" opera

I'd please ask people to don't write operators unless absolutely necessary. I used a certain tool which had its own config format, and it's "cloudnative" operator implemented CRDs of which multiple can exist and they would update the config file in some mounted volume. Such thing is a hell to debug. Why can't we just store the config file in configmap/ secret and listen to changes? (If we had a better templating solution than helm, I think quite a few operators wouldn't need to exist.)

pas 2y ago
> can't we just store the config file in configmap/ secret and listen to changes? isn't that what an operator also does basically? could you explain the problem with operators in more detail? thanks!
dilyevsky 2y ago
Operators that just render a config are a waste of resources. Operators that manage state of other operators (e.g Deployment) or external resources (e.g Crossplane) are a really convenient, developer-friendly way of solving infra automation challenges.