Snapshot Engine: volumeSnapshotClassName is hardcoded #417
Assignees
Comments
nicolasochem
added a commit
that referenced
this issue
Apr 13, 2022
from kube doc A volume snapshot can request a particular class by specifying the name of a VolumeSnapshotClass using the attribute volumeSnapshotClassName. If nothing is set, then the default class is used if available. https://kubernetes.io/docs/concepts/storage/volume-snapshots/
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tezos-k8s/snapshotEngine/createVolumeSnapshot.yaml
Line 9 in d7f78e3
Right now the volume snapshot class is manually created in the cluster. Pulumi needs to be creating it, because it is cluster scoped and we only want to create it once. So we don’t want it in tezos-k8s which would want to create it for every Helm deployment we do to the cluster.
So Pulumi needs to create it and it would give it a name. That name needs to be passed into values.y which would then have to get it into the VolumeSnapshot resource defined in createVolumeSnapshot.yaml
See https://aws.amazon.com/blogs/containers/using-ebs-snapshots-for-persistent-storage-with-your-eks-cluster/#:~:text=Step%204%3A[…]ass%20and%20Snapshot
The text was updated successfully, but these errors were encountered: