forgejo-next: use PV/PVC local chart for v{10,9,7} #500

Closed

GhostPLACEHOLDER wants to merge 0 commits from refs/pull/65/head2d0621f94b10bf066db8d46e0c49cbd493059eae into mainb7623d4bc2060d7314b1fa148acb2e859c9894df

GhostPLACEHOLDER commented

2025-05-29 20:27:14 +00:00

First-time contributor

The diff is empty when comparing with main, meaning it is a refactor with no change.

git checkout main
for i in 7 9 10 ; do kustomize build --load-restrictor  LoadRestrictionsNone forgejo-next-v$i > /tmp/before-$i.txt ; done
git checkout wip-pvc
for i in 7 9 10 ; do helm template --set-string major=$i charts/pvc > forgejo-next-v$i/pvc.yaml ; kustomize build --load-restrictor  LoadRestrictionsNone forgejo-next-v$i > /tmp/after-$i.txt ; diff -u /tmp/before-$i.txt /tmp/after-$i.txt ; done

Prevent the existing PV/PVC from being removed during reconciliation.

 for r in pv pvc ; do for s in {local-,}v{7,9,10} ; do kubectl annotate $r -n forgejo-next forgejo-next-$s kustomize.toolkit.fluxcd.io/prune=disabled ; done ; done
persistentvolume/forgejo-next-local-v7 annotated
persistentvolume/forgejo-next-local-v9 annotated
persistentvolume/forgejo-next-local-v10 annotated
persistentvolume/forgejo-next-v7 annotated
persistentvolume/forgejo-next-v9 annotated
persistentvolume/forgejo-next-v10 annotated
persistentvolumeclaim/forgejo-next-local-v7 annotated
persistentvolumeclaim/forgejo-next-local-v9 annotated
persistentvolumeclaim/forgejo-next-local-v10 annotated
persistentvolumeclaim/forgejo-next-v7 annotated
persistentvolumeclaim/forgejo-next-v9 annotated
persistentvolumeclaim/forgejo-next-v10 annotated

The diff is empty when comparing with main, meaning it is a refactor with no change. ```sh git checkout main for i in 7 9 10 ; do kustomize build --load-restrictor LoadRestrictionsNone forgejo-next-v$i > /tmp/before-$i.txt ; done git checkout wip-pvc for i in 7 9 10 ; do helm template --set-string major=$i charts/pvc > forgejo-next-v$i/pvc.yaml ; kustomize build --load-restrictor LoadRestrictionsNone forgejo-next-v$i > /tmp/after-$i.txt ; diff -u /tmp/before-$i.txt /tmp/after-$i.txt ; done ``` Prevent the existing PV/PVC from being removed during reconciliation. ```sh for r in pv pvc ; do for s in {local-,}v{7,9,10} ; do kubectl annotate $r -n forgejo-next forgejo-next-$s kustomize.toolkit.fluxcd.io/prune=disabled ; done ; done persistentvolume/forgejo-next-local-v7 annotated persistentvolume/forgejo-next-local-v9 annotated persistentvolume/forgejo-next-local-v10 annotated persistentvolume/forgejo-next-v7 annotated persistentvolume/forgejo-next-v9 annotated persistentvolume/forgejo-next-v10 annotated persistentvolumeclaim/forgejo-next-local-v7 annotated persistentvolumeclaim/forgejo-next-local-v9 annotated persistentvolumeclaim/forgejo-next-local-v10 annotated persistentvolumeclaim/forgejo-next-v7 annotated persistentvolumeclaim/forgejo-next-v9 annotated persistentvolumeclaim/forgejo-next-v10 annotated ```

GhostPLACEHOLDER commented

2025-05-29 20:27:15 +00:00

Author

First-time contributor

does the PVC chart deploy the NFS and local PVCs?

GhostPLACEHOLDER commented

2025-05-29 20:27:15 +00:00

Author

First-time contributor

does the PVC chart deploy the NFS and local PVCs?

Yes they do. local is used and nfs is on standby. Or used for backup.

> does the PVC chart deploy the NFS and local PVCs? Yes they do. local is used and nfs is on standby. Or used for backup.

root closed this pull request

2025-05-29 20:27:15 +00:00

GhostPLACEHOLDER commented

2025-05-29 20:27:15 +00:00

Author

First-time contributor

the Forgejo release should be depends on the PVC chart

Good catch, I forgot again.

45e958aed4..2d0621f94b

> the Forgejo release should be depends on the PVC chart Good catch, I forgot again. https://code.forgejo.org/infrastructure/k8s-cluster/compare/45e958aed41a6b4a8f2f5fb08f0e289b6484b374..2d0621f94b10bf066db8d46e0c49cbd493059eae