non-rolling update, i.e. kill pod before starting new

wave-k8s / wave

Kubernetes configuration tracking controller

Apache License 2.0

681 stars 81 forks source link

non-rolling update, i.e. kill pod before starting new #131

Closed jgm-ktg closed 7 months ago

jgm-ktg commented 2 years ago

I have a pod that depends on a non-sharable volume.

Wave starts a new pod which never comes up because of this.

I'd like an annotation where the deployment is marked for a non-rolling update.

Possible? New feature?

github-actions[bot] commented 1 year ago

This issue has been inactive for 60 days. If the issue is still relevant please comment to re-activate the issue. If no action is taken within 7 days, the issue will be marked closed.

jabdoa2 commented 7 months ago

This is something you can configure on your statefulset/daemonset/deployment via Strategy. See: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy