Text-only cleanup after the upgrade campaign. Updates stale version strings, prose, and comments to the verified current facts; no Kubernetes behavior or version pins changed except the kubectl toolchain bump (below). Verified facts applied: k3s v1.36.4+k3s1, Debian 13 trixie, Cilium 1.20.1 / Gateway API v1.6.1, Longhorn 1.12.1, node RAM 24 GiB, dedicated virtio2 SSD etcd disk per node, Velero chart 12.x / v1.18, Grafana 13.2.0. - Version strings across infra/ and platform/ READMEs + comments - kubectl toolchain 1.31.4 -> 1.36.4 (devcontainer/ci/conformance versions.env; 1.31 vs a 1.36 cluster exceeded the +-1 skew) - Retired-single-apps-Kustomization refs -> apps-wave-0/1/2 + apps-vms with per-wave SOPS decryption (flux/clusters docs + bootstrap.sh) - COMPLETED/historical banners on the three executed plan docs - Resolved TODO(WS-SEC) markers -> Renovate-maintained ranges - Appended dated DECISIONS-LOG entry (2026-08-30) superseding the 2026-08-26 LIVE STATE line Left as revalidation items (not blind-edited): external-snapshotter v8.2.0 vs 1.36, Cilium ext_authz/forward-auth relevance under 1.20.1, conformance ImageVolume feature-gate assertions under 1.36. Co-Authored-By: Claude Opus 4.8 <[email protected]>
44 lines
1.6 KiB
YAML
44 lines
1.6 KiB
YAML
---
|
|
# CloudNativePG operator (ghcr.io/cloudnative-pg images — NOT Bitnami, unaffected by the F-KY1 purge).
|
|
# Installs the postgresql.cnpg.io CRDs + a cluster-wide operator. The keycloak database itself is a
|
|
# `Cluster` CR carried by platform-config (dependsOn platform) — the controllers/configs split
|
|
# (F-MON1): a CR of a CRD this HelmRelease registers must NOT apply in the same pass.
|
|
apiVersion: helm.toolkit.fluxcd.io/v2
|
|
kind: HelmRelease
|
|
metadata:
|
|
name: cloudnative-pg
|
|
namespace: cnpg-system
|
|
spec:
|
|
interval: 30m
|
|
chart:
|
|
spec:
|
|
chart: cloudnative-pg
|
|
version: ">=0.22.0 <1.0.0" # Renovate-maintained range (bring-up is past; team uses ranges, not exact pins)
|
|
sourceRef:
|
|
kind: HelmRepository
|
|
name: cloudnative-pg
|
|
namespace: cnpg-system
|
|
install:
|
|
remediation:
|
|
retries: 3
|
|
upgrade:
|
|
remediation:
|
|
retries: 3
|
|
values:
|
|
# Avoid a full Postgres switchover on future operator minor bumps: update the instance-manager
|
|
# binary in place rather than recreating the pod (lands in the cnpg-controller-manager-config CM).
|
|
config:
|
|
data:
|
|
ENABLE_INSTANCE_MANAGER_INPLACE_UPDATES: "true"
|
|
# Single operator replica is plenty for a home cluster; it only reconciles CRs.
|
|
replicaCount: 1
|
|
resources:
|
|
requests:
|
|
cpu: 50m
|
|
memory: 100Mi
|
|
limits:
|
|
memory: 256Mi
|
|
# Expose operator metrics so the ServiceMonitor (platform-config) can scrape DB/operator health.
|
|
monitoring:
|
|
podMonitorEnabled: false # we ship a ServiceMonitor for the Cluster instead (docs/10)
|