Change for deployment rollout

[vbotingnon]

Hello, for my project it made more sense to do with deployments so that the service is not unavailable.

[TheYkk]

Hi Valdir thanks for your pr, but what if user only has a pod object?

[vbotingnon]

One option would be to implement an alternative for him to configure via POD or Deployments. Thus, it started to work only with deployments, which ensures that the service does not go down.

[TheYkk]

If you can add pod restart , I would like to merge this pr.

[almson]

I don't think synator should restart or redeploy anythings. Restarting on secret/config update is a general problem that should be solved by a separate operator (or, ideally, kubernetes itself).

[TheYkk]

I created synator because K8s can't do this.

[almson]

@TheYkk Then you should create another controller called, eg, "Rystartor" which handles restarting of pods/deployments. It would have nothing to do with Synator and would track both automatic and manual changes to ConfigMaps and Secrets.

Why do you think putting two unrelated pieces of functionality into the same controller is a good idea?