History

Erich Blume 1bdfca0f22 Add CloudNativePG operator via ArgoCD (Phase 1 Step 6) - Add CloudNativePG Application using multi-source Helm pattern - Helm chart from upstream cloudnative-pg repo - Values file from our git repo for customization - Manual sync policy consistent with other workload apps Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>		2026-01-19 08:06:33 -08:00
..
README.md	Add CloudNativePG operator via ArgoCD (Phase 1 Step 6)	2026-01-19 08:06:33 -08:00
values.yaml	Add CloudNativePG operator via ArgoCD (Phase 1 Step 6)	2026-01-19 08:06:33 -08:00

README.md

CloudNativePG Operator

Kubernetes operator for managing PostgreSQL clusters with high availability.

Source

Helm chart: cloudnative-pg from https://cloudnative-pg.github.io/charts
Documentation: https://cloudnative-pg.io/documentation/

Deployment

Managed via ArgoCD Application using Helm source (not kustomize). The Application points directly to the upstream Helm repository.

ArgoCD CLI Commands

# Check application status
argocd app get cloudnative-pg

# Trigger a sync
argocd app sync cloudnative-pg

# View deployment history
argocd app history cloudnative-pg

Verification

# Check operator pod is running
kubectl get pods -n cnpg-system

# Check operator logs
kubectl logs -n cnpg-system -l app.kubernetes.io/name=cloudnative-pg

# Check CRDs are installed
kubectl get crd | grep cnpg

Files

File	Description
`values.yaml`	Helm values for customization
`README.md`	This file

Notes

The operator is deployed to cnpg-system namespace
PostgreSQL clusters are created separately using the Cluster CRD (see Step 7)
No secrets required for the operator itself