Skip to content
logo
Percona Operator for PostgreSQL
Percona Operator for PostgreSQL 1.3.0 (2022-08-04)
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)
        • Release Highlights
        • Improvements
        • Bugs Fixed
        • Supported platforms
      • 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)

    • Release Highlights
    • Improvements
    • Bugs Fixed
    • Supported platforms

    Percona Operator for PostgreSQL 1.3.0¶

    • Date

      August 4, 2022

    • Installation

      Percona Operator for PostgreSQL

    Release Highlights¶

    • The automated upgrade is now disabled by default to prevent an unplanned downtimes for user applications and to provide defaults more focused on strict user’s control over the cluster

    • Flexible anti-affinity configuration is now available, which allows the Operator to isolate PostgreSQL cluster instances on different Kubernetes nodes or to increase its availability by placing PostgreSQL instances in different availability zones

    Improvements¶

    • K8SPG-155: Flexible anti-affinity configuration

    • K8SPG-196: Add possibility for postgres user to connect to PostgreSQL through PgBouncer with a new pgBouncer.exposePostgresUser Custom Resource option

    • K8SPG-218: The automated upgrade is now disabled by default to prevent an unplanned downtimes for user applications and to provide defaults more focused on strict user’s contol over the cluster; also the user is now able to turn off sending data to the Version Service server

    • K8SPG-226: A new build and testing guide allows user to easily experiment with the source code of the Operator

    Bugs Fixed¶

    • K8SPG-178: Fix the bug in the instruction on passing custom configuration options for PostgreSQL which made it usable for the new cluster only

    • K8SPG-193: Fix the bug which caused the Operator crash without pgReplicas section in Custom Resource definition

    • K8SPG-197: Fix the bug which caused the Operator to make connection requests to Version Service even with disabled Smart Update

    • K8SPG-207: Fix the bug due to which restoring S3 backup from storage with self-signed certificates didn’t work, by introducing the special backup.storages.verifyTLS option to address this issue

    Supported platforms¶

    The following platforms were tested and are officially supported by the Operator 1.3.0:

    • Google Kubernetes Engine (GKE) 1.21 - 1.24

    • Amazon Elastic Container Service for Kubernetes (EKS) 1.20 - 1.22

    • OpenShift 4.7 - 4.10

    This list only includes the platforms that the Percona Operators are specifically tested on as part of the release process. Other Kubernetes flavors and versions depend on the backward compatibility offered by Kubernetes itself.

    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.