Alauda build of CloudNativePG
  • English

    • Installation

    This page covers installing the Alauda build of CloudNativePG operator. Once the operator is installed, you can deploy your first PostgreSQL cluster by applying a Cluster CR (Functions guide coming in a later release).

    TOC

    PrerequisitesInstall via the platform catalog (recommended)Verify the installNext

    Prerequisites

    • An Alauda Container Platform (ACP) cluster, version 4.3 or later.
    • Cluster admin or platform admin access.
    • The cloudnative-pg package downloaded for your version (.tgz) — typically installed via the platform catalog UI.
    • A block-mode StorageClass available in the target cluster (e.g. global-topolvmsc).
    Web Console
    kubectl
    1. In the left navigation bar, go to Marketplace > Operator Hub.
    2. Select your target cluster.
    3. Search for CloudNativePG under the platform catalog source.
    4. Click Install.
    5. In the install dialog, accept the suggested namespace cnpg-system (the bundle declares this via the operatorframework.io/suggested-namespace annotation), select channel stable, install plan approval Automatic, and confirm.
    6. Wait until the operator's CSV reaches phase Succeeded and the cnpg-controller-manager deployment is 1/1 Ready.

    Verify the install

    After CSV is Succeeded:

    kubectl get csv -n cnpg-system
kubectl get deploy cnpg-controller-manager -n cnpg-system
kubectl get pods -n cnpg-system

    Expected:

    • One CSV cloudnative-pg.<version> with phase Succeeded.
    • Deployment cnpg-controller-manager with 1/1 ready replicas.
    • One operator pod cnpg-controller-manager-<hash> Running.

    Check the operator's environment for the ACP-specific defaults:

    kubectl get deploy cnpg-controller-manager -n cnpg-system \
  -o jsonpath='{.spec.template.spec.containers[0].env}' | python3 -c "
import json,sys
[print(e['name'], '=', e.get('value','')) for e in json.load(sys.stdin)
 if e['name'] in ('ENABLE_IMAGE_REWRITE_TOLERANCE','POSTGRES_IMAGE_NAME','PGBOUNCER_IMAGE_NAME')]"

    You should see:

    • ENABLE_IMAGE_REWRITE_TOLERANCE = true
    • POSTGRES_IMAGE_NAME = build-harbor.alauda.cn/middleware/cnpg/postgresql:18.3-standard-trixie
    • PGBOUNCER_IMAGE_NAME = build-harbor.alauda.cn/middleware/cnpg/pgbouncer:1.25.1

    If POSTGRES_IMAGE_NAME carries a timestamp tag (e.g. 18.3-202605070509-standard-trixie) or ENABLE_IMAGE_REWRITE_TOLERANCE is missing, you are on a pre-v1.29.0-acp.1 build. See Upgrade for the remediation procedure.

    Next

    A "Create a Cluster" walkthrough and Troubleshooting reference are scheduled for a future docs release. For now, the architecture page covers the Cluster CR model and the upgrade page includes diagnostic procedures for common install issues.