You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since I run pvc without storageClassName, AWS-EKS automatically set my pvc with gp2 storageClassName which is AWS-EBS basic name.
Typically, when using a storage type like NFS, you define the PV directly, reference it to the PVC, and do not use a StorageClass.
StorageClass is primarily used to dynamically provision block storage provided by cloud providers (e.g. AWS, GCP, Azure). Network file systems such as NFS typically do not support dynamic provisioning and require PVs to be set up and managed in advance.
Solved
Setting the NFS PV's storageClassName to an empty string ("") indicates that the StorageClass is not used.
apiVersion: v1kind: PersistentVolumeClaimmetadata:
name: pgadmin-pvcspec:
accessModes:
- ReadWriteManyresources:
requests:
storage: 100MistorageClassName: ""# Set empty string like this
Since I bound chat db pv and pvc with gp2 storageclass, it still doesn't work :(
![image](https://private-user-images.githubusercontent.com/29156882/288345504-6ad803e3-7a74-49bd-930a-637c3ba836a2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ5Njk3MTgsIm5iZiI6MTcyNDk2OTQxOCwicGF0aCI6Ii8yOTE1Njg4Mi8yODgzNDU1MDQtNmFkODAzZTMtN2E3NC00OWJkLTkzMGEtNjM3YzNiYTgzNmEyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODI5VDIyMTAxOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWU5ZGYxY2QwZmE4MzlhMTFiMDY3ZjIyMzI3ZWRlOTJiZGQxN2M2ZjZiNTU1ODE1ZmEzYzg2MTkyMjQxNDMxNTgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.R0ktySYJ9J4ALWPacXrdw5xCGd0KAoEkHilMKujoivk)
![image](https://private-user-images.githubusercontent.com/29156882/288345552-04f2e2aa-843e-492d-a94a-237737b68d58.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ5Njk3MTgsIm5iZiI6MTcyNDk2OTQxOCwicGF0aCI6Ii8yOTE1Njg4Mi8yODgzNDU1NTItMDRmMmUyYWEtODQzZS00OTJkLWE5NGEtMjM3NzM3YjY4ZDU4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODI5VDIyMTAxOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTAwYmQxNTQyOWVkYmZmNWJjNjUwMWJhMzAwMDgxMGM1NTEwYjVjYjA0MDRkMmI5MGFkNmMxZjk1YzM5MGUxYWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.l1yXg7gw_QmaCjQKtcEibnD514Vk1X9S0OlOGp4y2ko)
The text was updated successfully, but these errors were encountered: