Unable to use own PVC for postgres #598

New Issue

2024-01-10T00:26:27Z

tweekzilla commented

2024-01-10 00:26:27 +00:00

(Migrated from gitea.com)

The helm chart seems to insist on creating it's own PVC vs using one that I've created previously - I suspect I'm doing something wrong in the values.yaml file:

Values.yaml

postgresql:
  enabled: true
  global:
    postgresql:
      auth:
        password: gitea
        database: gitea
        username: gitea
      service:
        ports:
          postgresql: 5432
  primary:
    persistence:
      enabled: true
      claimName: gitea-dbdata-tn

POD DESCRIPTION:

Volumes:
data:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: data-gitea-postgresql-0
ReadOnly: false

The helm chart seems to insist on creating it's own PVC vs using one that I've created previously - I suspect I'm doing something wrong in the values.yaml file: Values.yaml ``` postgresql: enabled: true global: postgresql: auth: password: gitea database: gitea username: gitea service: ports: postgresql: 5432 primary: persistence: enabled: true claimName: gitea-dbdata-tn ``` POD DESCRIPTION: Volumes: data: Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace) ClaimName: data-gitea-postgresql-0 ReadOnly: false

justusbunsi commented

2024-01-10 05:25:04 +00:00

(Migrated from gitea.com)

Try existingClaim (cee371d106/bitnami/postgresql/values.yaml (L663))

Try `existingClaim` (https://github.com/bitnami/charts/blob/cee371d10674dc61de5adda4a79f4c9a1e8f85d0/bitnami/postgresql/values.yaml#L663)

👍 1

pat-s commented

2024-01-10 09:43:33 +00:00

(Migrated from gitea.com)

On a fresh deployment primary.persistence should work, i.e. in subsequent updates the persistent volume should be re-used then without having to use existingClaim. Did you by chance enabled persistence after the initial deployment? The existing ClaimName of "data-gitea-postgresql-0" suggests that as this is auto-generated one. If you define persistence after the first start, you need to use existingClaim then or wipe everything and start from scratch.

On a fresh deployment `primary.persistence` should work, i.e. in subsequent updates the persistent volume should be re-used then without having to use `existingClaim`. Did you by chance enabled persistence after the initial deployment? The existing `ClaimName` of "data-gitea-postgresql-0" suggests that as this is auto-generated one. If you define persistence after the first start, you need to use `existingClaim` then or wipe everything and start from scratch.

pat-s commented

2024-01-22 09:43:28 +00:00

(Migrated from gitea.com)

Closing due to no reply.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: lunny/helm-chart#598