CODEWITHSUNDEEP
kubernetes
liotur
liotur

Reputation: 923

Should Kubernetes operator delete resources which are not managed by it?

I have my application deployed on Kubernetes cluster, managed by operator (A). I am mounting secrets with ssl key materials to the deployment, so application could access to the content.

I have separate operator (B) deployment, which is responsible to create those secrets with the ssl key materials. Now I have a use case where my secrets are recreated by operator (B), and it deletes/restarts the pods, which managed by operator (A).

I am trying understand - is it common practice to allow separately deployed operator delete pods?

My perception was that operator should work only with resources it manages, nothing more.

Upvotes: 0

Views: 631

Answers (1)

Mikołaj Głodziak
Mikołaj Głodziak

Reputation: 5267

Community wiki to summarise the topic.

If it is as you say:

both operators are proprietary,

it is impossible to give a definite yes or no answer. Everything will depend on what is really going on there, and we are not able to check and evaluate it.

Look at the well provided comments by David Maze:

That sort of seems like a bug...but also, Pods are pretty disposable and the usual expectation is that a ReplicaSet or another controller will recreate them...?

Note that the essence of the Kubernetes controller model is that the controller looks at the current state of the Kubernetes configuration store (not changes or events, just which objects exist and which don't) and tries to make the things it manages match that, so if the controller believes it should manage some external resource and there's not a matching Kubernetes object, it could delete it.

Upvotes: 1

Related Questions