Skip to content
logo
Percona Operator for PostgreSQL
Welcome
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
      • 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)

    Percona Operator for PostgreSQL¶

    Kubernetes have added a way to manage containerized systems, including database clusters. This management is achieved by controllers, declared in configuration files. These controllers provide automation with the ability to create objects, such as a container or a group of containers called pods, to listen for an specific event and then perform a task.

    This automation adds a level of complexity to the container-based architecture and stateful applications, such as a database. A Kubernetes Operator is a special type of controller introduced to simplify complex deployments. The Operator extends the Kubernetes API with custom resources.

    The Percona Operator for PostgreSQL is based on best practices for configuration and setup of a Percona Distribution for PostgreSQL cluster. The benefits of the Operator are many, but saving time and delivering a consistent and vetted environment is key.

    Requirements¶

    • System Requirements

    • Design and architecture

    • Comparison with other solutions

    Quickstart guides¶

    • Install on Minikube

    • Install on Google Kubernetes Engine (GKE)

    • Install with Helm

    Installation guides¶

    • Generic Kubernetes installation

    • Install on OpenShift

    Configuration¶

    • Application and system users

    • Changing PostgreSQL Options

    • Anti-affinity and tolerations

    • Transport Encryption (TLS/SSL)

    • Telemetry

    Management¶

    • 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

    HOWTOs¶

    • How to deploy a standby cluster for Disaster Recovery

    • Percona Operator for PostgreSQL single-namespace and multi-namespace deployment

    • Using PostgreSQL tablespaces with Percona Operator for PostgreSQL

    Reference¶

    • Custom Resource options

    • Operator installation options

    • Percona certified images

    • Frequently Asked Questions

    • Release Notes

    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.