refactor: remove explicit StorageClass selection

Previously PVCs need to define storage class explicitly because if
a PVC was created before Longhorn is ready, it will stay pending forever
until we delete and recreate it (ArgoCD didn't have sync wave for
ApplicationSet back then).

Kubernetes 1.28 has retroactive assignment of a default StorageClass for
existing unbound persistent volume claims without any storage class assigned.

https://kubernetes.io/blog/2023/08/15/kubernetes-v1-28-release/#automatic-retroactive-assignment-of-a-default-storageclass-graduates-to-stable
This commit is contained in:
Khue Doan 2023-11-19 12:04:10 +07:00
parent f4ee4be035
commit e28bada08e
6 changed files with 0 additions and 11 deletions

View File

@ -44,7 +44,6 @@ dendrite:
addresses:
- nats://matrix-nats:4222
persistence:
storageClass: longhorn
logs:
capacity: 1Gi
media:
@ -63,7 +62,6 @@ dendrite:
postgresqlPassword: dendrite
persistence:
enabled: true
storageClass: longhorn
accessModes:
- ReadWriteOnce
size: 5Gi

View File

@ -24,8 +24,3 @@ gitea:
ROOT_URL: https://git.khuedoan.com
webhook:
ALLOWED_HOST_LIST: private
persistence:
storageClass: longhorn
postgresql:
persistence:
storageClass: longhorn

View File

@ -42,6 +42,5 @@ docker-registry:
persistence:
enabled: true
size: 10Gi
storageClass: longhorn
garbageCollect:
enabled: true

View File

@ -43,7 +43,6 @@ spec:
- name: shared-data
volumeClaimTemplate:
spec:
storageClassName: longhorn
accessModes:
- ReadWriteOnce
resources:

View File

@ -36,7 +36,6 @@ spec:
- name: shared-data
volumeClaimTemplate:
spec:
storageClassName: longhorn
accessModes:
- ReadWriteOnce
resources:

View File

@ -260,7 +260,6 @@ kind: PersistentVolumeClaim
metadata:
name: vault-file
spec:
storageClassName: longhorn
accessModes:
- ReadWriteOnce
resources: