Add support for Storage Classes and pre-provisioned PVs #21
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.
Add support for Storage Classes and pre-provisioned PVs
This PR adds support for two features for the Netbird Management pod PVC:
Storage Class
Users may wish to use a non-default Storage Class.
.Values.management.persistentVolume.storageClass
to populate the.spec.storageClassName
field in the PVC manifeststorageClassName
field, i.e. empty string (""
) has subtly different behaviour to no value (null
).storageClassName
field, thus the change is non-breakingPre-existing Persistent Volumes
Some users may wish to provision volumes separately from the chart (i.e. static provisioning), for example when migrating configuration data between environments or storage types.
.Values.management.persistentVolume.existingPVName
to populate the.spec.volumeName
field in the PVC manifest