Service Deployment v0.18.0 with StatefulSets #171
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update allows us to leverage the existing chart as a StatefulSet with full PVC support baked in. The main difference between these two kinds of deployment is that:
volumeTemplate
that lets us create a PVC per pod. These volumes get re-attached to the pod with the same name when upgrades happen / pods move between k8s cluster nodes.helm delete
) this retains the volumes (this is the default in the docs) - a user should configure this to suit their own needs!