Support for restart policy in sftpgo Helm Chart

[agmimidi]

Hi,

We are seeing an issue where when we upgrade our chart the new pod gets stuck in Container Creating state.

This happens because the old pod is still there and holds access to the persistent volume claim. The only way around this at the moment is to force delete the old pod. Adding support for pod restart policy or allowing deploying as a state-full set should solve the issue.

Cheers and thanks for the chart :) Angelos

[sagikazarmark]

@agmimidi which chart are you talking about?

[agmimidi]

https://github.com/sagikazarmark/helm-charts/tree/master/charts/sftpgo

Tis on the issue title 😁

[agmimidi]

@sagikazarmark Did you have a chance to look into this?

Cheers, Angelos

[sagikazarmark]

Sorry, I have not.

I'm a bit confused though: Isn't deployment strategy that you want to change: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy