Port CloudNative-PG off Helm to direct release manifest #268

Merged

eblume merged 1 commit from feature/cnpg-direct-source into main

2026-02-25 17:37:54 -08:00

eblume commented

2026-02-25 17:30:55 -08:00

Owner

Summary

Point ArgoCD app directly at forge-mirrored upstream repo (mirrors/cloudnative-pg) instead of the Helm charts repo
Use directory.include to select the specific release manifest (cnpg-1.27.1.yaml) from the releases/ directory
No vendored files, no Helm — upgrades are a two-line change (targetRevision + directory.include)
Delete unused values.yaml (was empty, all Helm defaults)

Deployment and Testing

Register mirror repo in ArgoCD: argocd repo add ssh://forgejo@forge.ops.eblu.me:2222/mirrors/cloudnative-pg.git --ssh-private-key-path <key>
argocd app set cloudnative-pg --revision feature/cnpg-direct-source && argocd app sync cloudnative-pg
Verify operator pod running: kubectl get pods -n cnpg-system --context=minikube-indri
Verify CRDs exist: kubectl get crd --context=minikube-indri | grep cnpg
Verify existing clusters healthy: kubectl get clusters -A --context=minikube-indri
After merge: argocd app set cloudnative-pg --revision main && argocd app sync cloudnative-pg

Notes

The forge mirror was created via mise run mirror-create from https://github.com/cloudnative-pg/cloudnative-pg.git
ArgoCD may need the mirror repo added to its known repositories if the credential template doesn't already match mirrors/*

## Summary - Point ArgoCD app directly at forge-mirrored upstream repo (`mirrors/cloudnative-pg`) instead of the Helm charts repo - Use `directory.include` to select the specific release manifest (`cnpg-1.27.1.yaml`) from the `releases/` directory - No vendored files, no Helm — upgrades are a two-line change (`targetRevision` + `directory.include`) - Delete unused `values.yaml` (was empty, all Helm defaults) ## Deployment and Testing - [ ] Register mirror repo in ArgoCD: `argocd repo add ssh://forgejo@forge.ops.eblu.me:2222/mirrors/cloudnative-pg.git --ssh-private-key-path <key>` - [ ] `argocd app set cloudnative-pg --revision feature/cnpg-direct-source && argocd app sync cloudnative-pg` - [ ] Verify operator pod running: `kubectl get pods -n cnpg-system --context=minikube-indri` - [ ] Verify CRDs exist: `kubectl get crd --context=minikube-indri | grep cnpg` - [ ] Verify existing clusters healthy: `kubectl get clusters -A --context=minikube-indri` - [ ] After merge: `argocd app set cloudnative-pg --revision main && argocd app sync cloudnative-pg` ## Notes - The forge mirror was created via `mise run mirror-create` from `https://github.com/cloudnative-pg/cloudnative-pg.git` - ArgoCD may need the mirror repo added to its known repositories if the credential template doesn't already match `mirrors/*`

eblume added 1 commit

2026-02-25 17:30:55 -08:00

Port CloudNative-PG operator from Helm chart to direct release manifest 9b8bef64a6

Point the ArgoCD app directly at the forge-mirrored upstream repo
(mirrors/cloudnative-pg) using directory.include to select the specific
release manifest. This eliminates both the Helm chart dependency and
the need to vendor large manifest files. Upgrades become a two-line
change: targetRevision and directory.include.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>