Closed simonspg closed 4 years ago
It is. If you enable persistence and don't specify the PV names, the stack PVCs asks a PV for the default StorageClass.
Agreed. I wondered if I was being clear enough. I’m still learning all the terminology. What if I want to establish a dynamic persistent volume claim for a storageClass that is not the default? K3s comes with local-path as the default storage class, and I have added the managed-nfs-storage storageClass. I’m not sure if k3s uses local-path storage, so I left it as the default.
From: Carlos Eduardo notifications@github.com Sent: Monday, June 22, 2020 14:52 To: carlosedp/cluster-monitoring cluster-monitoring@noreply.github.com Cc: Paul Simons paul@thesimonet.org; Author author@noreply.github.com Subject: Re: [carlosedp/cluster-monitoring] Support for dynamic persistent volume claims (#68)
It is. If you enable persistence and don't specify the PV names, the stack PVCs asks a PV for the default StorageClass.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/carlosedp/cluster-monitoring/issues/68#issuecomment-647787418 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ALIAV27Y4RQHLR7BNAY4WJDRX7G6JANCNFSM4OFBW24A . https://github.com/notifications/beacon/ALIAV26AUSZ7FGA5T7NBPRTRX7G6JA5CNFSM4OFBW24KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE2OHHGQ.gif
Added on ad1d165. You can define the StorageClass name.
A convenient enhancement would be support for dynamic persistent storage. storageClassName instead of volumeName.