Skip to content
logo
Percona Operator for PostgreSQL
Operator installation options
Initializing search
    percona/k8spg-docs
    percona/k8spg-docs
    • Welcome
      • System Requirements
      • Design and architecture
      • Comparison with other solutions
      • Install on Minikube
      • Install on Google Kubernetes Engine (GKE)
      • Install with Helm
      • Generic Kubernetes installation
      • Install on OpenShift
      • Application and system users
      • Changing PostgreSQL Options
      • Anti-affinity and tolerations
      • Transport Encryption (TLS/SSL)
      • Telemetry
      • Backup and restore
      • Upgrade Percona Distribution for PostgreSQL and the Operator
      • Horizontal and vertical scaling
      • Monitor with Percona Monitoring and Management (PMM)
      • Restart or pause the cluster
      • Deploy a standby cluster for Disaster Recovery
      • Provide Percona Operator for PostgreSQL single-namespace and multi-namespace deployment
      • Use PostgreSQL tablespaces with Percona Operator for PostgreSQL
      • Custom Resource options
      • Operator installation options
        • General Configuration
      • Percona certified images
      • Frequently Asked Questions
      • Release notes index
      • Percona Operator for PostgreSQL 1.3.0 (2022-08-04)
      • Percona Operator for PostgreSQL 1.2.0 (2022-04-06)
      • Percona Operator for PostgreSQL 1.1.0 (2021-12-07)
      • Percona Operator for PostgreSQL 1.0.0 (2021-10-07)
      • Percona Operator for PostgreSQL 0.2.0 (2021-08-12)
      • Percona Operator for PostgreSQL 0.1.0 (2021-05-10)

    • General Configuration

    The Operator installation options¶

    When installing The Operator, you can customize additional configuration options. These options are specified in deploy/operator.yaml file and already have reasonable defaults, so most users have no need modifying them.

    General Configuration¶

    These variables affect the general configuration of the PostgreSQL Operator.

    Name Default Required Description
    archive_mode true ✔ If true, enables archive logging on all newly created clusters
    archive_timeout 60 ✔ Set to a value in seconds to configure the timeout threshold for archiving
    ccp_image_pull_secret "" Name of a Secret with credentials for the container image registries for the PostgreSQL cluster
    ccp_image_pull_secret_manifest "" A path to the Secret manifest to be installed in each namespace (optional)
    create_rbac true ✔ Set to true if the installer should create the RBAC resources required to run the PostgreSQL Operator
    delete_operator_namespace false If true, the Operator namespace (one defined using the pgo_operator_namespace variable) will be deleted when uninstalling the Operator
    delete_watched_namespaces false If true, the Operator watched namespaces (ones defined using the namespace variable) will be deleted when uninstalling the Operator
    disable_telemetry false If true, gathering telemetry by the Operator will be disabled
    namespace pgo A comma delimited string of all the namespaces the Operator should manage
    namespace_mode disabled Determines which namespace permissions are assigned to the PostgreSQL Operator using a ClusterRole; can be dynamic, readonly, and disabled
    pgo_image_prefix percona/percona-postgresql-operator ✔ The image prefix used when creating containers for the Operator (apiserver, operator, scheduler, etc.)
    pgo_image_pull_policy Always The policy for updating the Operator images
    pgo_image_pull_secret "" Name of a Secret with credentials for the Operator’s container image registries
    pgo_image_pull_secret_manifest "" Optionally provides a path to the Secret manifest to be installed in each namespace
    pgo_image_tag 1.3.0 ✔ Configures the image tag used when creating the Operator’s containers (apiserver, operator, scheduler, etc.)
    pgo_operator_namespace pgo ✔ The namespace where the Operator will be deployed

    Contact Us

    For free technical help, visit the Percona Community Forum.

    To report bugs or submit feature requests, open a JIRA ticket.

    For paid support and managed or consulting services , contact Percona Sales.


    Last update: 2023-02-09
    Back to top
    Percona LLC and/or its affiliates, © 2009 - 2022
    Made with Material for MkDocs

    Cookie consent

    We use cookies to recognize your repeated visits and preferences, as well as to measure the effectiveness of our documentation and whether users find what they're searching for. With your consent, you're helping us to make our documentation better.