all:
  children:
    cephs:
      hosts:
        instance: null
    computes:
      hosts:
        instance: null
    controllers:
      hosts:
        instance: null
    zuul_unreachable:
      hosts: {}
  hosts:
    instance:
      ansible_connection: ssh
      ansible_host: 162.253.55.204
      ansible_port: 22
      ansible_python_interpreter: auto
      ansible_user: zuul
      ceph_conf_overrides:
      - option: mon allow pool size one
        section: global
        value: true
      - option: osd crush chooseleaf type
        section: global
        value: 0
      - option: auth allow insecure global id reclaim
        section: mon
        value: false
      ceph_csi_rbd_helm_values:
        provisioner:
          replicaCount: 1
      ceph_fsid: 4837cbf8-4f90-4300-b3f6-726c9b9f89b4
      ceph_osd_devices:
      - /dev/ceph-{{ inventory_hostname_short }}-osd0/data
      - /dev/ceph-{{ inventory_hostname_short }}-osd1/data
      - /dev/ceph-{{ inventory_hostname_short }}-osd2/data
      cilium_helm_values:
        operator:
          replicas: 1
      cilium_ipv4_cidr: 172.24.0.0/16
      csi_driver: local-path-provisioner
      kube_vip_address: 172.17.0.100
      kube_vip_interface: '{{ ansible_facts[''default_ipv4''].interface }}'
      kubernetes_hostname: '{{ ansible_facts[''default_ipv4''].address }}'
      molecule_scenario: csi
      nodepool:
        az: nova
        cloud: public
        external_id: 74a985a5-a36f-4eda-85a3-3ddb2c837d7d
        host_id: 413ad91e6120ae81306de27e59dcefd40ab96f06b8665fea7030ef8f
        interface_ip: 162.253.55.204
        label: ubuntu-jammy
        node_properties: {}
        private_ipv4: 162.253.55.204
        private_ipv6: null
        provider: yul1
        public_ipv4: 162.253.55.204
        public_ipv6: 2604:e100:1:0:f816:3eff:fea2:49ec
        region: ca-ymq-1
        slot: null
      zuul_node:
        az: nova
        cloud: public
        external_id: 74a985a5-a36f-4eda-85a3-3ddb2c837d7d
        host_id: 413ad91e6120ae81306de27e59dcefd40ab96f06b8665fea7030ef8f
        interface_ip: 162.253.55.204
        label: ubuntu-jammy
        node_properties: {}
        private_ipv4: 162.253.55.204
        private_ipv6: null
        provider: yul1
        public_ipv4: 162.253.55.204
        public_ipv6: 2604:e100:1:0:f816:3eff:fea2:49ec
        region: ca-ymq-1
        slot: null
        uuid: null
  vars:
    ceph_conf_overrides:
    - option: mon allow pool size one
      section: global
      value: true
    - option: osd crush chooseleaf type
      section: global
      value: 0
    - option: auth allow insecure global id reclaim
      section: mon
      value: false
    ceph_csi_rbd_helm_values:
      provisioner:
        replicaCount: 1
    ceph_fsid: 4837cbf8-4f90-4300-b3f6-726c9b9f89b4
    ceph_osd_devices:
    - /dev/ceph-{{ inventory_hostname_short }}-osd0/data
    - /dev/ceph-{{ inventory_hostname_short }}-osd1/data
    - /dev/ceph-{{ inventory_hostname_short }}-osd2/data
    cilium_helm_values:
      operator:
        replicas: 1
    cilium_ipv4_cidr: 172.24.0.0/16
    csi_driver: local-path-provisioner
    kube_vip_address: 172.17.0.100
    kube_vip_interface: '{{ ansible_facts[''default_ipv4''].interface }}'
    kubernetes_hostname: '{{ ansible_facts[''default_ipv4''].address }}'
    molecule_scenario: csi
    zuul:
      _inheritance_path:
      - '<Job base explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: zuul-config/zuul.d/jobs.yaml@main#1>'
      - '<Job molecule explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: vexxhost/zuul-jobs/zuul.d/ansible-jobs.yaml@main#1>'
      - '<Job atmosphere-molecule explicit: None implied: {MatchAny:{ImpliedBranchMatcher:stable/2023.1}}
        source: vexxhost/atmosphere/.zuul.yaml@stable/2023.1#17>'
      - '<Job atmosphere-molecule-csi explicit: None implied: {MatchAny:{ImpliedBranchMatcher:stable/2023.1}}
        source: vexxhost/atmosphere/.zuul.yaml@stable/2023.1#53>'
      - '<Job atmosphere-molecule-csi-local-path-provisioner explicit: None implied:
        {MatchAny:{ImpliedBranchMatcher:stable/2023.1}} source: vexxhost/atmosphere/.zuul.yaml@stable/2023.1#60>'
      - '<Job atmosphere-molecule-csi-local-path-provisioner explicit: None implied:
        None source: vexxhost/atmosphere/.zuul.yaml@stable/2023.1#72>'
      ansible_version: '9'
      attempts: 1
      branch: stable/2023.1
      build: 2c7fba1b9702407b8b5b36b8cc9d33dd
      build_refs:
      - branch: stable/2023.1
        change: '2595'
        change_message: "Update pxc (stable/2023.1)\n\n> \u2139\uFE0F **Note**\n>
          \n> This PR body was truncated due to platform limits.\n\nThis PR contains
          the following updates:\n\n| Package | Type | Update | Change | [Age](https://docs.renovatebot.com/merge-confidence/)
          | [Confidence](https://docs.renovatebot.com/merge-confidence/) |\n|---|---|---|---|---|---|\n|
          docker.io/percona/haproxy |  | patch | `2.8.14` \u2192 `2.8.18` | ![age](https://developer.mend.io/api/mc/badges/age/docker/docker.io%2fpercona%2fhaproxy/2.8.18?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/docker.io%2fpercona%2fhaproxy/2.8.14/2.8.18?slim=true)
          |\n| docker.io/percona/percona-xtradb-cluster-operator |  | minor | `1.17.0`
          \u2192 `1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/docker/docker.io%2fpercona%2fpercona-xtradb-cluster-operator/1.19.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/docker.io%2fpercona%2fpercona-xtradb-cluster-operator/1.17.0/1.19.0?slim=true)
          |\n| [github.com/percona/percona-xtradb-cluster-operator](https://redirect.github.com/percona/percona-xtradb-cluster-operator)
          | require | minor | `v1.16.1` \u2192 `v1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fpercona%2fpercona-xtradb-cluster-operator/v1.19.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fpercona%2fpercona-xtradb-cluster-operator/v1.16.1/v1.19.0?slim=true)
          |\n| [percona/percona-xtradb-cluster-operator](https://redirect.github.com/percona/percona-xtradb-cluster-operator)
          |  | minor | `1.17.0` \u2192 `1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/github-releases/percona%2fpercona-xtradb-cluster-operator/1.19.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/github-releases/percona%2fpercona-xtradb-cluster-operator/1.17.0/1.19.0?slim=true)
          |\n| [pxc-operator](https://docs.percona.com/percona-operator-for-mysql/pxc/)
          ([source](https://redirect.github.com/percona/percona-helm-charts)) |  |
          minor | `1.17.0` \u2192 `1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/helm/pxc-operator/1.19.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/helm/pxc-operator/1.17.0/1.19.0?slim=true)
          |\n| quay.io/prometheus/mysqld-exporter |  | minor | `v0.17.0` \u2192 `v0.18.0`
          | ![age](https://developer.mend.io/api/mc/badges/age/docker/quay.io%2fprometheus%2fmysqld-exporter/v0.18.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/quay.io%2fprometheus%2fmysqld-exporter/v0.17.0/v0.18.0?slim=true)
          |\n\n---\n\n### Release Notes\n\n<details>\n<summary>percona/percona-xtradb-cluster-operator
          (github.com/percona/percona-xtradb-cluster-operator)</summary>\n\n### [`v1.19.0`](https://redirect.github.com/percona/percona-xtradb-cluster-operator/releases/tag/v1.19.0)\n\n[Compare
          Source](https://redirect.github.com/percona/percona-xtradb-cluster-operator/compare/v1.18.0...v1.19.0)\n\n#####
          Release Highlights\n\nThis release of Percona Operator for MySQL based on
          Percona XtraDB Cluster includes the following new features and improvements:\n\n#####
          Ensure data security for Percona XtraDB Cluster 8.4 with data-at-rest encryption\n\nData
          at rest encryption ensures that sensitive information stored on disk remains
          protected from unauthorized access, even if the physical media is compromised.
          It is a foundational safeguard for compliance, trust and security in modern
          database environments.\n\nThe Operator supports data at rest encryption
          for MySQL 8.0 with HashiCorp Vault using the `keyring_vault` *plugin*. Now,
          it also supports data at rest encryption for MySQL 8.4, leveraging the `keyring_vault`
          *component*.\n\nThis enhancement enables you to benefit from the rich feature
          set of the latest major version of Percona XtraDB Cluster 8.4 while ensuring
          your sensitive data is secured. In doing so, you can meet compliance requirements
          and protect critical information without added operational complexity. Learn
          how to [configure data at rest encryption for Percona XtraDB Cluster 8.4](https://docs.percona.com/percona-operator-for-mysql/pxc/encryption-setup.html).\n\n#####
          Percona XtraDB Cluster 8.4 is now fully supported\n\nPercona XtraDB Cluster
          8.4 is now fully supported and recommended for production deployments. Starting
          with this release, it becomes the default version for all new database cluster
          deployments using the Operator. This support enables you to benefit from
          its latest features, performance improvements, and enhanced security.\n\n#####
          Use your own CA certificates for TLS verification\n\nYou can now use your
          organization\u2019s custom Certificate Authority (CA) to securely verify
          TLS communication with S3 storage during backups and restores.\n\nThe configuration
          is straightforward: create the Secret that stores your custom CA and certificates
          to authorize in the S3 storage. Then reference this Secret and specify the
          CA certificate in the `caBundle` option in the Operator Custom Resource.
          The Operator will verify TLS communication against it.\n\nHere's the example
          configuration:\n\n```yml\nstorages:\n  minio-s3:\n    type: s3\n    verifyTLS:
          true\n    s3:\n      caBundle:\n         name: minio-ca-bundle\n         key:
          tls.crt\n```\n\nWith this improvement, you ensure the following:\n\n- Security
          without compromise \u2013 no more bypassing identity checks.\n- Alignment
          with your internal standards \u2013 use the CA your company already trusts.\n-
          Confidence in backup and restore flows \u2013 every S3 interaction is properly
          verified.\n\nRead more about the use of own CA certificates in our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/backups-storage.html#configure-tls-verification-with-custom-certificates-for-s3-storage)\n\n#####
          Configure duration for certificates issued by cert-manager\n\nBy default,
          the `cert-manager` generates certificates valid for 90 days. You now have
          more control over certificate lifetimes and can configure their custom duration
          when you create a new cluster. This way you can align with your organization's
          security and compliance policies.\n\nUse the following Custom Resource options
          to configure certificate duration:\n\n- `.spec.tls.certValidityDuration`
          \u2013 validity period for generated certificates\n- `.spec.tls.caValidityDuration`
          \u2013 validity period for the Certificate Authority (CA)\n\n```yaml\n  tls:\n
          \   enabled: true\n    certValidityDuration: 2160h\n    caValidityDuration:
          26280h\n```\n\nNote that the Operator enforces minimum durations to certificates:\n\n-
          For TLS certificates \u2013 1 hour\n- For CA certificate \u2013 730 hours.\n\nAlso,
          we don't recommend setting duration to exactly 1 hour to prevent certificate
          generation issues. Read more about rules and limitations about certificate
          duration configuration in our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/tls-cert-manager.html#customize-certificate-duration-for-cert-manager).\n\nThis
          improvement empowers you to fine-tune certificate lifetimes while keeping
          your cluster secure and stable.\n\n##### Security context for ProxySQL sidecar
          containers\n\nYou can now define the security context for ProxySQL sidecar
          containers in the Operator, reducing the risk of unsecured sidecars bypassing
          Pod restrictions. This improvement lets you set user IDs, privileges, and
          filesystem access directly, ensuring compliance and strengthening Pod security.\n\nConfigure
          the security context in your custom resource. For example:\n\n```yaml\nspec:\n
          \ proxysql:\n       sidecars:\n          securityContext:\n              privileged:
          false\n```\n\nWith this change, you enforce safer defaults across your deployments
          and close security gaps at the Pod level.\n\n##### Improved load balancing
          with ProxySQL scheduler (tech preview)\n\nThe Operator now integrates with
          the external `pxc_scheduler_handler` tool to improve query routing. This
          feature is currently in tech preview, so we recommend experimenting with
          it in test or staging environments before using it in production.\n\nWith
          this scheduler you get finer control over how your SQL queries are routed
          within your PXC cluster:\n\n- SELECT queries (that don't use FOR UPDATE)
          are intelligently distributed across all PXC nodes\u2014or all nodes except
          the writer, depending on your settings.\n- Non-SELECT queries and SELECT
          FOR UPDATE statements are routed to the writer node.\n- You don't have to
          micromanage the writer role: the scheduler automatically ensures only one
          writer is active at any time.\n\nThis means you could see:\n\n- better performance
          and higher throughput from distributing query loads\n- greater reliability
          with no single point of failure\n\n* Improved cluster health through early
          detection of replication lag and node issues\n\n- more efficient use of
          your resources and hardware\n- a smoother, more predictable experience for
          everyone using the database\n\nSee our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/proxysql-conf.html#proxysql-scheduler-tech-preview)
          for full information about the scheduler behavior and setup.\n\nThe previous
          internal scheduler remains enabled by default to maintain backward compatibility.
          You can switch to the new one when you're ready to benefit from smarter
          query handling.\n\n##### Customize HAProxy backend health check intervals
          and failover behavior\n\nYou can now control how quickly HAProxy detects
          and reacts to node failures. Instead of waiting the default 20 seconds while
          HAProxy performs the failover, you can tune health checks to cut that down
          to just a few seconds. That means your applications recover faster, and
          users don't get stuck with hanging sessions when a node goes down.\n\nYou
          no longer need to override the entire HAProxy configuration to achieve this
          \u2014 the operator now gives you simple, direct options in the Custom Resource
          specification:\n\n```yaml\nhaproxy:  \n   healthCheck:\n       interval:
          10000\n       rise: 1\n       fall: 2\n```\n\nBy adjusting how often checks
          run and how many failures or successes mark a node as \u201Cdown\u201D or
          \u201Cup,\u201D you get faster failover, cleaner client handling, and easier
          configuration that is safe to upgrade and tailored to your environment.\n\n#####
          Switch from HAProxy to ProxySQL at runtime\n\nYou can now switch from HAProxy
          to ProxySQL without redeploying your Percona XtraDB Cluster. Previously,
          you had to choose ProxySQL only at startup. Now ProxySQL has the `caching_sha2_password`
          as the default authentication plugin, which gives you the flexibility to
          start with HAProxy and migrate to ProxySQL later as your needs evolve.\n\nWith
          this release, ProxySQL also includes a new [scheduler](#improved-load-balancing-with-proxysql-scheduler-tech-preview)
          that enhances SQL awareness, automates read/write splitting, and handles
          failovers more intelligently. This leads to faster queries, increased reliability,
          and more efficient cluster resource usage.\n\n**Which proxy should you choose?**\n\n-
          **HAProxy:** Choose HAProxy if you need a lightweight, TCP-level load balancer
          with minimal configuration. Note that for read/write splitting, your clients
          must connect to different HAProxy ports based on the query type.\n- **ProxySQL:**
          Opt for ProxySQL if you want built-in read/write splitting, advanced query-level
          control, and automated failover logic right out of the box.\n\nEach proxy
          brings its own resource requirements and advantages. We offer [additional
          guidance](https://docs.percona.com/percona-operator-for-mysql/pxc/load-balancing.html#what-load-balancer-to-use)
          on selecting the right proxy for your environment, plus [detailed recommendations](https://docs.percona.com/percona-operator-for-mysql/pxc/proxy-switching.html)
          on resource planning and best practices. Review these carefully to ensure
          your choice fits your operational and performance needs.\n\nTo switch between
          proxies, update your Custom Resource to set `haproxy.enabled` to `false`
          and `proxysql.enabled` to `true`. Apply the changes, and the Operator will
          handle the transition for you by restarting the relevant proxy Pods.\n\nWith
          this improvement you now control your proxy choice at runtime, and ProxySQL
          brings smarter routing and resilience right into the Operator.\n\n#####
          ProxySQL 3 support\n\nYou can now deploy ProxySQL 3 with Percona Operator
          for MySQL. This gives you more flexibility and control over how your applications
          connect to MySQL inside Kubernetes. Here\u2019s what you get:\n\n- Dual\u2011password
          support enables you to introduce a new password while the old one is still
          valid. As a result, you can rotate passwords without downtime\n- Enhanced
          event and query logging gives you real\u2011time visibility into query behavior
          and application traffic.\n- ProxySQL now logs the actual values bound to
          prepared statements. This helps you debug queries more effectively, since
          you see what data was passed instead of just placeholders\n- Event logs
          now include metadata about ProxySQL version and format. This makes it easier
          to track and audit logs across upgrades in your Operator\u2011managed deployments.\n\n#####
          Direct-access backups: Improved performance and reliability with sidecars
          (tech preview)\n\nBy default, the Operator makes backups using the SST method.
          This creates a separate backup Pod with Percona XtraBackup, while the database
          node enters Donor state and stops serving client requests. SST backups can
          also fail with cryptic network errors, making root cause analysis and recovery
          difficult.\n\nStarting with version 1.19.0, you can make backups via the
          XtraBackup sidecar container. The Operator deploys a sidecar with XtraBackup
          inside each Percona XtraDB Cluster Pod. This sidecar makes a backup and
          uploads it to the remote backup storage. The database Pod doesn\u2019t change
          its state to Donor and keeps accepting client requests.\n\nUsing the sidecar
          method provides a direct access to data thus boosting backup performance.
          The sidecar container constantly runs in the database Pod, so you have constant
          access to logs and status, which simplifies troubleshooting.\n\nTo enable
          the XtraBackup sidecar container backup method, set `PXCO_FEATURE_GATES=XtrabackupSidecar=true`
          environment variable in the Operator Deployment.\nThis functionality is
          in the tech preview stage and currently supports only cloud storages. We
          encourage you to try it out in your testing or staging environments and
          leave your feedback.\n\nFuture enhancements such as support of PVC volumes,
          backup encryption and incremental backups are planned for future releases.\n\nTo
          learn more about XtraBackup sidecar container backup method, see our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/backups.html#xtrabackup-sidecar-method-tech-preview).\n\n#####
          Ensure only up to date data is served during backups\n\nWhen a node donates
          data during backups or SST, it enters into the DONOR state. At this point,
          the node should no longer handle client connections. HAProxy's external
          check correctly blocked new connections to the Donor node but allowed existing
          sessions to remain active. Those lingering sessions could return slow or
          outdated results.\n\nThe HAProxy default configuration now includes the
          `on-marked-down shutdown-sessions` directive. As soon as HAProxy marks a
          node as down, all active connections are immediately closed and clients
          reconnect to remaining active nodes. This ensures that only fresh, up to
          date data is served during backups.\n\n##### Automatic cleanup of backup
          and restore Jobs and associated Pods\n\nThe Operator creates a dedicated
          Job and Pod for every backup and restore operation. Previously, these Jobs
          and Pods remained in the cluster even after the operation was finished,
          and you had to manually delete them to free up resources.\n\nNow, you can
          offload this task to the Operator. Specify a time-to-live (TTL) for backup
          and restore Jobs once the operation is finished. When the TTL expires, the
          Operator automatically deletes the Job and its associated Pod.\n\nModify
          your Custom Resource as follows:\n\n```yaml\nbackup:\n  image: perconalab/percona-xtradb-cluster-operator:main-pxc8.0-backup\n
          \ ttlSecondsAfterFinished: 3600\n```\n\nThis setting is global. It applies
          to all on-demand and scheduled backups, and all restores.\n\nThe Operator
          also ensures reliability: if a backup or restore takes longer than the configured
          TTL, it applies the `internal.percona.com/keep-job` finalizer to allow the
          operation to finish. After the operation completes either with the `Succeeded`
          or the `Failed` status, the finalizer is removed and the Job is cleaned
          up.\n\nThis improvement reduces manual maintenance overhead, gives you control
          over the processes lifetime for debugging or auditing purposes and helps
          keep your cluster healthy and efficient. By reducing unnecessary resource
          buildup, you gain smoother operations, lower maintenance overhead and improved
          reliability in production environments.\n\n##### Improved backup identification
          for point-in-time recovery readiness\n\nWhen a backup contains binlog gaps,
          the Operator now creates a `<backup-name>.pitr-not-ready` file in the backup
          storage. This file makes it easy to identify which backups are appropriate
          for point in time recovery both in the storage and when listing backup objects.\n\nBefore
          starting a restore, the Operator checks for this marker file and blocks
          unsafe restores, protecting you from incomplete recovery attempts. If needed,
          you can override this safeguard by adding the `percona.com/unsafe-pitr`
          annotation to the Restore object. Use this override with caution, as this
          is an unsafe configuration.\n\n##### Attach external PVCs for shared data
          access across applications and the database cluster\n\nSometimes your database
          needs more than its own internal storage. For example, it needs access to
          reference files, shared configuration files or lookup tables generated outside
          the database but still essential for queries and procedures.\n\nYou can
          now attach auxiliary pre-existing PVCs and mount that external data directly
          into your database, ProxySQL or HAProxy pods in a clean, declarative way
          using the Custom Resource.\n\nThis example configuration shows how to attach
          external PVC to the XtraDB Cluster Pods:\n\n```yaml\npxc:\n  extraPVCs:\n
          \   - name: extra-data-volume\n      claimName: my-extra-storage\n      mountPath:
          /var/lib/mysql-extra\n      readOnly: false\n```\n\nThis improvement gives
          you a reliable way to separate internal database storage from external domain
          data, update shared datasets independently, and still benefit from the Operator\u2019s
          automation and resilience.\n\n##### Customize password generation by the
          Operator\n\nBy default, the Operator generates user passwords using alphanumeric
          characters plus a set of special symbols. Some tools such as MySQL Prometheus
          Exporter or mysqlsh don't support certain symbols, which can make those
          passwords invalid.\n\nTo improve compatibility and user experience, you
          can now customize password generation parameters in the Custom Resource:\n\n```yaml\nspec:\n
          passwordGenerationOptions:\n   symbols: \"!#$%&()*+,-.<=>?@&#8203;[]^_{}~\"\n
          \  maxLength: 20\n   minLength: 16\n```\n\nThis enhancement lets you keep
          the convenience of automated password generation and at the same time ensure
          compliance with the tools and environments you integrate with the Operator.\n\n#####
          Configure memory allocator in the Operator\n\nBy default, Percona Operator
          for XtraDB Cluster uses the system allocator (`libc`) to manage memory.
          While this works for most cases, alternative allocators such as `jemalloc`
          and `tcmalloc` can improve performance and reduce fragmentation in high-traffic
          workloads.\n\nTo have more flexibility, you can now configure the memory
          allocator directly in the Custom Resource:\n\n```yaml\nspec:\n   pxc:\n
          \    mysqlAllocator: jemalloc\n```\n\nSupported values are:\n\n- `jemalloc`\n-
          `tcmalloc`\n- `libc` (default, used when no value is set)\n\nIf you have
          already configured the memory allocator via the environment variable, the
          Operator will respect that setting and use it instead of the Custom Resource
          value.\n\nThis enhancement lets you fine-tune memory management for your
          cluster while keeping compatibility with existing configurations.\n\n#####
          Deprecation, rename, removal\n\n**Removed in 1.19.0:**\n\n- `proxysql.readinessDelaySec`
          and `proxysql.livenessDelaySec` fields are removed as redundant\n\n**Deprecated
          (will be removed in 1.22.0):**\n\n- `pxc.livenessDelaySec`. Use [`pxc.livenessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pxclivenessprobesinitialdelayseconds)\n-
          `pxc.readinessDelaySec`. Use [`pxc.readinessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pxcreadinessprobesinitialdelayseconds)\n-
          `haproxy.livenessDelaySec`. Use [`haproxy.livenessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#haproxylivenessprobesinitialdelayseconds)\n-
          `haproxy.readinessDelaySec`. Use [`haproxy.readinessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#haproxyreadinessprobesinitialdelayseconds)\n\n#####
          Changelog\n\n##### New Features\n\n- [K8SPXC-1332](https://perconadev.atlassian.net/browse/K8SPXC-1332)
          - Added the ability to load custom SSL certificates for backup operations
          to S3 storage. This enables secure communication with S3-compatible storage
          using the certificates approved and trusted by your company (Thank you Azam
          Abdoelbasier for submitting this request).\n- [K8SPXC-1494](https://perconadev.atlassian.net/browse/K8SPXC-1494)
          - Added the ability to configure the duration of TLS certificates created
          by `cert-manager`. This allows users to customize certificate lifecycles
          to meet their specific security requirements.\n- [K8SPXC-1576](https://perconadev.atlassian.net/browse/K8SPXC-1576)
          - Added the ability to use the XtraBackup sidecar container instead of SST
          for creating backups. This provides an alternative, potentially more efficient
          backup method.\n- [K8SPXC-1688](https://perconadev.atlassian.net/browse/K8SPXC-1688)
          - Added ability to mount pre-existing auxiliary PVCs as volumes to database
          and proxy pods. This facilitates easier integration with external data and
          storage resources (Thank you Emin AKTAS for submitting the request and contributing
          to it).\n- [K8SPXC-1733](https://perconadev.atlassian.net/browse/K8SPXC-1733)
          - Added the ability to customize password generation parameters, such as
          length and character sets via the Custom Resource. This ensures smooth operation
          of the tools with specific requirements towards password and leverages the
          automatic password generation of the Operator (Thank you user fydrah for
          submitting the request and contributing to it).\n- [K8SPXC-1734](https://perconadev.atlassian.net/browse/K8SPXC-1734)
          - Introduced configurable HAProxy backend health check parameters that can
          be tuned without overriding the entire configuration. This simplifies performance
          tuning for high-availability setups (Thank you Tim Stoop for submitting
          the request and contributing to it).\n\n##### Improvements\n\n- [K8SPXC-735](https://perconadev.atlassian.net/browse/K8SPXC-735)
          - Added the support of the `pxc_scheduler_handler` ProxySQL scheduler for
          SQL-aware routing and effective read/write splitting. This allows for better
          utilization of resources by distributing read-only traffic across the entire
          cluster while routing write requests only to the writer node.\n- [K8SPXC-992](https://perconadev.atlassian.net/browse/K8SPXC-992)
          - Improved binlog naming to prevent potential collisions between different
          collectors. The updated naming convention ensures unique and consistent
          identification of binary log files in storage.\n- [K8SPXC-1144](https://perconadev.atlassian.net/browse/K8SPXC-1144)
          - Introduced a mechanism to mark S3 backups as PITR-unready if binlog gaps
          are detected. This prevents users from attempting invalid point-in-time
          recoveries using inconsistent backups.\n- [K8SPXC-1214](https://perconadev.atlassian.net/browse/K8SPXC-1214)
          - Added an option to automatically clean up completed backup and restore
          jobs and their associated pods. This improvement helps reduce pressure on
          the Kubernetes API by removing stale resources (Thank you Alexandre Barth
          for reporting this issue).\n- [K8SPXC-1319](https://perconadev.atlassian.net/browse/K8SPXC-1319)
          - Enhanced the operator to support running multiple backup restores for
          different clusters in parallel. This removes a previous limitation that
          blocked concurrent restore operations across the environment.\n- [K8SPXC-1327](https://perconadev.atlassian.net/browse/K8SPXC-1327)
          - Added the ability to change the memory allocator for MySQL to improve
          memory management efficiency. This change helps optimize the overall memory
          footprint of PXC pods.\n- [K8SPXC-1373](https://perconadev.atlassian.net/browse/K8SPXC-1373)
          - Improved core dump handling to ensure that crashed instances can recover
          more reliably after an SST. This enhancement aids in diagnosing and recovering
          from unexpected server failures.\n- [K8SPXC-1431](https://perconadev.atlassian.net/browse/K8SPXC-1431)
          - Improved the delete-backup finalizer logic to correctly handle the deletion
          of on-demand backup PVCs.\n- [K8SPXC-1470](https://perconadev.atlassian.net/browse/K8SPXC-1470)
          - Added the ability to switch between HAProxy and ProxySQL within an existing
          cluster. This provides users with more flexibility to change their load-balancing
          solution as their needs evolve.\n- [K8SPXC-1511](https://perconadev.atlassian.net/browse/K8SPXC-1511)
          - Added the support of data at rest encryption for Percona XtraDB Cluster
          8.4 via the `keyring vault` component. This change ensures compatibility
          with the latest security architecture of MySQL 8.4.\n- [K8SPXC-1525](https://perconadev.atlassian.net/browse/K8SPXC-1525)
          - Deprecated `pxc.livenessDelaySec` option in favor of more consistent liveness
          probe parameters. The Operator now prioritizes standard probe configurations
          to manage Pod lifecycle.\n- [K8SPXC-1568](https://perconadev.atlassian.net/browse/K8SPXC-1568)
          - Updated the Operator's password generation logic to prevent the '\\*'
          character from being used as the first character. This avoids potential
          issues with certain authentication plugins and command-line tools.\n- [K8SPXC-1594](https://perconadev.atlassian.net/browse/K8SPXC-1594)
          - Improved the database upgrade logic to prevent the controller from being
          blocked during the operation. This ensures that the Operator remains responsive
          to other cluster changes while an upgrade is in progress.\n- [K8SPXC-1628](https://perconadev.atlassian.net/browse/K8SPXC-1628)
          - Added support for `tcmalloc` as an alternative memory allocator in PXC
          images. This gives users additional options to tune and reduce the memory
          footprint of their database workloads.\n- [K8SPXC-1647](https://perconadev.atlassian.net/browse/K8SPXC-1647)
          - Implemented extended exit codes for garbd to provide better diagnostic
          information for different failure scenarios. This helps users identify the
          root cause of SST and joining issues faster.\n- [K8SPXC-1668](https://perconadev.atlassian.net/browse/K8SPXC-1668)
          - Added support for ProxySQL 3, providing users with access to the latest
          features and performance improvements of the load balancer.\n- [K8SPXC-1683](https://perconadev.atlassian.net/browse/K8SPXC-1683)
          - Expanded smart update tests to include PXC 8.4 and PMM 3, ensuring stable
          upgrade paths for the latest versions.\n- [K8SPXC-1703](https://perconadev.atlassian.net/browse/K8SPXC-1703)
          - Added the support of the `generateEmbeddedObjectMeta` option, improving
          the template handling for sidecars and extra PVCs (Thank you Emin AKTAS
          for reporting and contributing to this issue).\n- [K8SPXC-1748](https://perconadev.atlassian.net/browse/K8SPXC-1748)
          - Eliminated runtime CREATE FUNCTION statements in the PITR collector to
          avoid unnecessary Galera TOI (Total Order Isolation) events. This reduces
          the performance impact on the cluster when the PITR sidecar starts or restarts.\n\n#####
          Bugs Fixed\n\n- [K8SPXC-926](https://perconadev.atlassian.net/browse/K8SPXC-926)
          - Fixed an issue where a failed smart update on one cluster could block
          the Operator from managing other clusters in multi-cluster environments.
          The controller now handles update failures more gracefully without impacting
          independent resources.\n- [K8SPXC-1379](https://perconadev.atlassian.net/browse/K8SPXC-1379)
          - Fixed an issue where monit container resource values in ProxySQL pods
          did not correctly reflect the values specified in the PXC cluster definition.
          The operator now ensures that ProxySQL resource attributes are properly
          applied to the monitoring sidecar containers.\n- [K8SPXC-1424](https://perconadev.atlassian.net/browse/K8SPXC-1424)
          - Resolved a certificate renewal issue where CA certificates in TLS secrets
          could expire before server certificates were renewed. The Operator logic
          was updated to align renewal intervals for CA and server certificates when
          using cert-manager.\n- [K8SPXC-1581](https://perconadev.atlassian.net/browse/K8SPXC-1581)
          - Corrected the order of options in the restore prepare job to ensure that
          `--defaults-file` is passed as the first option to xtrabackup. This fix
          ensures that custom configuration files are correctly prioritized during
          the restore process.\n- [K8SPXC-1617](https://perconadev.atlassian.net/browse/K8SPXC-1617)
          - Fixed a binlog gap issue in Point-in-Time Recovery (PITR) that caused
          repeated test failures. Users are now advised to perform a full backup after
          each PITR restore to ensure data consistency and prevent gaps.\n- [K8SPXC-1632](https://perconadev.atlassian.net/browse/K8SPXC-1632)
          - Added missing SecurityContext configurations for ProxySQL sidecar containers
          to enhance pod security. This change ensures that all sidecars follow the
          defined security standards of the cluster.\n- [K8SPXC-1655](https://perconadev.atlassian.net/browse/K8SPXC-1655)
          - Fixed a failure in xtrabackup when using LZ4 compression on RHEL9-based
          Percona XtraDB Cluster images. The fix addresses compatibility issues with
          the latest compression libraries in the operating system environment.\n-
          [K8SPXC-1686](https://perconadev.atlassian.net/browse/K8SPXC-1686) - Improved
          backup error handling to ensure that providing an invalid Percona XtraBackup
          image results in a failed status. A new timeout field was introduced to
          prevent backup objects from hanging indefinitely in a starting state.\n-
          [K8SPXC-1687](https://perconadev.atlassian.net/browse/K8SPXC-1687) - Fixed
          the `copy-backup.sh` script to correctly handle and copy cloud-based backups
          stored in S3 or Azure. This ensures that the utility script works consistently
          across all supported storage types.\n- [K8SPXC-1701](https://perconadev.atlassian.net/browse/K8SPXC-1701)
          - Ensured that MySQL configurations are correctly mounted to the restore
          prepare job. This fix allows the restore process to use custom MySQL settings
          defined in the cluster (Thank you Emin AKTAS for reporting and contributing
          to this issue).\n- [K8SPXC-1702](https://perconadev.atlassian.net/browse/K8SPXC-1702)
          - Added the ability to override time zones for backup jobs. This resolves
          issues where time-dependent operations could fail due to missing timezone
          definitions (Thank you Emin AKTAS for reporting and contributing to this
          issue).\n- [K8SPXC-1721](https://perconadev.atlassian.net/browse/K8SPXC-1721)
          - Added a sleep interval to the recovery loop to prevent high CPU usage
          spikes when containers restart.\n- [K8SPXC-1725](https://perconadev.atlassian.net/browse/K8SPXC-1725)
          - Fixed a condition where a cluster could return stalled data during a backup
          or SST operation by adding the on-marked-down shutdown-sessions directive
          to HAProxy default configuration. This ensures that only fresh, up to date
          data is served during backups.\n- [K8SPXC-1726](https://perconadev.atlassian.net/browse/K8SPXC-1726)
          - Resolved a deployment breakage in the Operator version 1.18.0 via Helm
          caused by PMM 3 client incompatibilities. The fix ensures a smoother upgrade
          path for users migrating to newer versions of PMM (Thank you Antonio Falzarano
          for reporting and contributing to this issue).\n- [K8SPXC-1760](https://perconadev.atlassian.net/browse/K8SPXC-1760)
          - Fixed the handling of the crVersion field in the Helm chart templates.
          The Operator now correctly considers the version defined in `values.yaml`
          when generating the cluster configuration.\n- [K8SPXC-1771](https://perconadev.atlassian.net/browse/K8SPXC-1771)
          - Fixed the issue with excessive logging by the backup controller when backups
          are suspended or resumed due to an unready cluster. This improves log readability
          and reduces unnecessary diagnostic noise.\n- [K8SPXC-1772](https://perconadev.atlassian.net/browse/K8SPXC-1772)
          - Fixed a state transition bug where unsuspended backups could move directly
          from 'Starting' to 'Succeeded' without entering the 'Running' state. This
          ensures accurate tracking and visibility of the backup process status.\n\n#####
          Documentation Improvements\n\n- [K8SPXC-1747](https://perconadev.atlassian.net/browse/K8SPXC-1747)
          - Improved the documentation with the information about available environment
          variables for cluster components and the Operator. Documented the `S3_WORKERS_LIMIT`
          environment variable to allow throttling of backup deletions.\n- [K8SPXC-1661](https://perconadev.atlassian.net/browse/K8SPXC-1661)
          - Updated the operator documentation to reflect that PMM 3 uses service
          accounts instead of API keys. This ensures that users can correctly configure
          monitoring integration with the latest versions of PMM.\n- [K8SPXC-1663](https://perconadev.atlassian.net/browse/K8SPXC-1663)
          - Improved documentation for Point-in-Time Recovery steps. The updated documentation
          properly separates and sequences the recovery instructions for improved
          readability.\n\n##### Supported Software\n\nThe Operator was developed and
          tested with the following software:\n\n- Percona XtraDB Cluster versions
          8.4.7-7.1, 8.0.44-35.1, and 5.7.44-31.65\n- Percona XtraBackup versions
          8.4.0-5.1, 8.0.35-34.1, and 2.4.29\n- HAProxy 2.8.17\n- ProxySQL 2.7.3-1.2,
          3.0.1-1.2\n- LogCollector based on fluent-bit 4.0.1-1\n- PMM Client 2.44.1-1
          and 3.5.0\n\nOther options may also work but have not been tested.\n\n#####
          Supported Platforms\n\nPercona Operators are designed for compatibility
          with all [CNCF-certified](https://www.cncf.io/training/certification/software-conformance/)
          Kubernetes distributions. Our release process includes targeted testing
          and validation on major cloud provider platforms and OpenShift, as detailed
          below:\n\n- [Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine)
          1.31 - 1.33\n- [Amazon Elastic Container Service for Kubernetes (EKS)](https://aws.amazon.com)
          1.32 - 1.34\n- [Azure Kubernetes Service (AKS)](https://azure.microsoft.com/en-us/services/kubernetes-service/)
          1.32 - 1.34\n- [OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift)
          4.17 - 4.20\n- [Minikube](https://minikube.sigs.k8s.io/docs/) 1.37.0 based
          on Kubernetes 1.34.0\n\nThis 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.\n\n### [`v1.18.0`](https://redirect.github.com/percona/percona-xtradb-cluster-operator/releases/tag/v1.18.0)\n\n[Compare
          Source](https://redirect.github.com/percona/percona-xtradb-cluster-operator/compare/v1.17.0...v1.18.0)\n\n#####
          Release Highlights\n\nThis release of Percona Operator for MySQL based on
          Percona XtraDB Cluster includes the following new features and improvements:\n\n#####
          PMM3 support\n\nThe Operator is natively integrated with [PMM 3](https://www.percona.com/doc/percona-monitoring-and-management/3/index.html),
          enabling you to monitor the health and performance of your Percona Distribution
          for MySQL deployment and at the same time enjoy enhanced performance, new
          features, and improved security that PMM 3 provides.\n\nNote that the Operator
          supports both PMM2 and PMM3. The decision on what PMM version is used depends
          on the authentication method you provide in the Operator configuration:
          PMM2 uses API keys while PMM3 uses service account token. If the Operator
          configuration contains both authentication methods with non-empty values,
          PMM3 takes the priority.\n\nTo use PMM, ensure that the PMM client image
          is compatible with the PMM Server version. Check [Percona certified images](https://docs.percona.com/percona-operator-for-mysql/pxc/images.html)
          for the correct client image.\n\nFor how to configure monitoring with PMM,
          see the [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/monitoring.html).\n\n#####
          Improved monitoring for clusters in multi-region or multi-namespace deployments
          in PMM\n\nNow you can define a custom name for your clusters deployed in
          different data centers. This name helps Percona Management and Monitoring
          (PMM) Server to correctly recognize clusters as connected and monitor them
          as one deployment. Similarly, PMM Server identifies clusters deployed with
          the same names in different namespaces as separate ones and correctly displays
          performance metrics for you on dashboards.\n\nTo assign a custom name, define
          this configuration in the Custom Resource manifest for your cluster:\n\n```yaml\nspec:\n
          \ pmm:\n    customClusterName: testClusterName\n```\n\n##### More resilient
          database restores without matching user Secrets\n\nYou no longer need matching
          user Secrets between your backup and your target cluster to perform a restore.
          The Operator now has a post-restore step that changes user passwords in
          the restored database to the ones from the local Secret. Also, it creates
          missing system users and adds missing grants.\n\nThis flow is the same regardless
          of whether you restore to the same cluster or to a completely new one.\n\nThe
          removal of this major roadblock to have a Secret for restores makes your
          disaster recovery process smoother and more reliable. This enhancement makes
          managing databases on Kubernetes more robust and operator-friendly.\n\n#####
          Improved backup retention for streamlined management of scheduled backups
          in cloud storage\n\nA new backup retention configuration gives you more
          control over how backups are managed in storage and retained in Kubernetes.\n\nWith
          the `deleteFromStorage` flag , you can disable automatic deletion from AWS
          S3 or Azure Blob storage and instead rely on native cloud lifecycle policies.
          This makes backup cleanup more efficient and better aligned with flexible
          storage strategies.\n\nThe legacy `keep` option is now deprecated and mapped
          to the new `retention` block for compatibility. We encourage you to start
          using the `backup.schedule.retention` configuration:\n\n```yaml\nschedule:\n
          \ - name: \"sat-night-backup\"\n    schedule: \"0 0 * * 6\"\n    retention:\n
          \     count: 3\n      type: count\n      deleteFromStorage: true\n    storageName:
          s3-us-west\n```\n\nNote that if you have both `backup.schedule.keep`  and
          `backup.schedule.retention`  defined, the `backup.schedule.retention` takes
          precedence.\n\n##### Added labels to identify the version of the Operator\n\nCustom
          Resource Definition (CRD) is compatible with the last three Operator versions.
          To know which Operator version is attached to it, we've added labels to
          all Custom Resource Definitions. The labels help you identify the current
          Operator version and decide if you need to update the CRD. To view the labels,
          run: `kubectl get crd perconaxtradbclusters.pxc.percona.com --show-labels`.\n\n#####
          Cross-site replication is now supported for Percona XtraDB Cluster 8.4\n\nCross-site
          replication is now available with Percona XtraDB Cluster 8.4.x, lifting
          one of the  limitations in the Operator for this database version. This
          enhancement marks a significant step toward general availability of Percona
          XtraDB Cluster 8.4 in the Operator by enabling multi-site deployments and
          improving resilience across distributed environments.\n\n##### Deprecation,
          Rename and Removal\n\n- The `pxc.expose.loadBalancerIP`, `haproxy.exposePrimary.loadBalancerIP`,
          `haproxy.exposeReplicas.loadBalancerIP` and `proxysql.expose.loadBalancerIP`
          keys are deprecated. The `loadBalancerIP` field is also deprecated upstream
          in Kubernetes\n  due to its inconsistent behavior across cloud providers
          and lack of dual-stack support. As a result, its usage is strongly discouraged.\n\n
          \ We recommend using cloud provider-specific annotations instead, as they
          offer more predictable and portable behavior for managing load balancer
          IP assignments.\n\n  The `pxc.expose.loadBalancerIP`, `haproxy.exposePrimary.loadBalancerIP`,
          `haproxy.exposeReplicas.loadBalancerIP` and `proxysql.expose.loadBalancerIP`
          keys are scheduled for removal in future releases.\n\n- The `backup.schedule.keep`
          field is deprecated and will be removed after release 1.21.0. We recommend
          using the `backup.schedule.retention` instead as follows:\n\n  ```yaml\n
          \ schedule:\n    - name: \"sat-night-backup\"\n      schedule: \"0 0 **
          6\"\n      retention:\n        count: 3\n        type: count\n        deleteFromStorage:
          true\n      storageName: s3-us-west\n  ```\n\n- New repositories for Percona
          XtraBackup and Logcollector\n\n  Now the Operator uses the official Percona
          Docker images for the `percona-xtrabackup` and `logcollector` components.
          Pay attention to the new image repositories when you upgrade the Operator
          and the database. Check the [Percona certified images](https://docs.percona.com/percona-operator-for-mysql/pxc/images.html)
          for exact image names.\n\n- Changes for Helm charts:\n\n  - PMM3 is now
          the default. To keep using PMM2, set the `pmm.tag: 2.44.1`\n  - If you install
          or upgrade the Operator with default manifests using Helm charts on Openshift
          4.19, you must use the `docker.io` registry prefix to guarantee successful
          download from the DockerHub `percona-xtradb-cluster` repository. Read the
          [Considerations for using OpenShift 4.19](#considerations-for-using-openshift-419)
          section for more information.\n\n##### Known limitations\n\n##### Considerations
          for using OpenShift 4.19\n\nStarting with OpenShift 4.19, the way images
          with not fully qualified names are pulled has changed for repositories that
          share the same repository name on DockerHub and Red Hat Marketplace. By
          default the tags are pulled from Red Hat Marketplace. Specifying not fully
          qualified image names may result in the `ImagePullBackOff` error.\n\n- **OLM
          installation:** Images are provided with the fully qualified names and are
          pulled from the Red Hat Marketplace/DockerHub registry.\n- **Manual install/update
          with default manifests:** Images must use the `docker.io` registry prefix
          to guarantee successful download from the Dockerhub `percona-xtradb-cluster`
          repository.\n\nSee our documentation for [manual installation](https://docs.percona.com/percona-operator-for-mysql/pxc/openshift.html#install-the-operator-via-the-command-line-interface)
          or [update](https://docs.percona.com/percona-operator-for-mysql/pxc/update_openshift.html#update-via-the-command-line-interface).\n\n#####
          Changleog\n\n##### New Features\n\n- [K8SPXC-1284](https://perconadev.atlassian.net/browse/K8SPXC-1284)
          - Add the ability to configure protocol for peer-list DNS SRV lookups\n\n-
          [K8SPXC-1599](https://perconadev.atlassian.net/browse/K8SPXC-1599) - Allowed
          setting `loadBalancerClass` service type and using a custom implementation
          of a load balancer rather than the cloud provider default one\n\n##### Improvements\n\n-
          [K8SPXC-1375](https://perconadev.atlassian.net/browse/K8SPXC-1375) - Added
          a new retention configuration to allow users to delegate backup cleanup
          to cloud lifecycle policies (Thank you user Tristan for reporting this issue)\n\n-
          [K8SPXC-1376](https://perconadev.atlassian.net/browse/K8SPXC-1376) - Added
          the ability to restore from backup without a matching Secret resource\n\n-
          [K8SPXC-1399](https://perconadev.atlassian.net/browse/K8SPXC-1399) - Added
          a documentation how to set up a disaster recovery system and transfer workloads
          between sites\n\n- [K8SPXC-1415](https://perconadev.atlassian.net/browse/K8SPXC-1415)
          - Updated the `percona-xtrabackup` image to use the official `percona-xtrabackup`
          Docker image\n\n- [K8SPXC-1430](https://perconadev.atlassian.net/browse/K8SPXC-1430)
          - Improved handling of autogenerated certificates depending on the `delete-ssl`
          finalizer configuration\n\n- [K8SPXC-1448](https://perconadev.atlassian.net/browse/K8SPXC-1448),
          [K8SPXC-1449](https://perconadev.atlassian.net/browse/K8SPXC-1449) - Improved
          the `pvc-resize` test by using a custom storage class for EKS, reducing
          errors and improving the quota handling during resize\n\n- [K8SPXC-1450](https://perconadev.atlassian.net/browse/K8SPXC-1450)
          - Improved PVC resizing behavior when reducing the storage size by reverting
          the values when the quota is reached\n\n- [K8SPXC-1472](https://perconadev.atlassian.net/browse/K8SPXC-1472)
          - Deprecated the `loadBalancerIP` field due to its deprecation upstream\n\n-
          [K8SPXC-1513](https://perconadev.atlassian.net/browse/K8SPXC-1513) - Added
          PXC 8.4 support for version service\n\n- [K8SPXC-1529](https://perconadev.atlassian.net/browse/K8SPXC-1529)
          - Added support for cross-site replication with MySQL 8.4.0 by adding the
          use of `authentication_policy` instead of `default_authentication_plugin`\n\n-
          [K8SPXC-1553](https://perconadev.atlassian.net/browse/K8SPXC-1553) - Added
          support for PMM v3\n\n- [K8SPXC-1560](https://perconadev.atlassian.net/browse/K8SPXC-1560)
          - Added the warning about CRDs not being upgraded automatically after helm
          upgrade to the output\n\n- [K8SPXC-1566](https://perconadev.atlassian.net/browse/K8SPXC-1566)
          - Improved reconciliation of replicationChannels without proxy Pods by starting
          the database Pod bypassing the proxy (Thank you Justin Reasoner for contributing
          to this issue)\n\n- [K8SPXC-1569](https://perconadev.atlassian.net/browse/K8SPXC-1569)
          - Added Labels for Custom Resource Definitions (CRD) to identify the Operator
          version attached to them\n\n- [K8SPXC-1597](https://perconadev.atlassian.net/browse/K8SPXC-1597)
          - Improve the scheduled backups behavior for a cluster in an unhealthy state
          by postponing the job until the cluster reports the healthy status\n\n-
          [K8SPXC-1605](https://perconadev.atlassian.net/browse/K8SPXC-1605) - Introduced
          Azure CLI for checking if backup objects/folders exist in Azure storage\n\n-
          [K8SPXC-1612](https://perconadev.atlassian.net/browse/K8SPXC-1612) - Added
          the `imagePullSecrets` for PMM image\n\n- [K8SPXC-1615](https://perconadev.atlassian.net/browse/K8SPXC-1615)
          - Added the ability to define a custom cluster name for `pmm-admin` component\n\n-
          [K8SPXC-1624](https://perconadev.atlassian.net/browse/K8SPXC-1624) - Deleted
          deprecated finalizers code\n\n- [K8SPXC-1669](https://perconadev.atlassian.net/browse/K8SPXC-1669)
          - Improve the backup flow by generating a default endpoint URL for a storage
          from a region if it is not provided (Thank you Bernard Grymonpon for reporting
          this issue)\n\n- [K8SPXC-1677](https://perconadev.atlassian.net/browse/K8SPXC-1677)
          - Document the changed behavior with pulling images for default manifests
          on OpenShift 4.19 and update install and update instructions\n\n##### Bugs
          Fixed\n\n- [K8SPXC-1312](https://perconadev.atlassian.net/browse/K8SPXC-1312)
          - Fixed the issue with labels not being updated automatically for point-in-time
          recovery deployment upon Custom Resource changes\n\n- [K8SPXC-1347](https://perconadev.atlassian.net/browse/K8SPXC-1347)
          - Fixed the issue with point-in-time recovery failing due to TLS configuration
          mismatch between the server and the point-in-time recovery job by configuring
          it to use TLS if is required by the server.\n\n- [K8SPXC-1382](https://perconadev.atlassian.net/browse/K8SPXC-1382)
          - Fixed the issue with backup failing on AWS if using IAM profile without
          credentialsSecret by using credentialsSecret only when explicitly specified
          and relying on IAM roles instead (Thank you Itiel Olenick for reporting
          this issue)\n\n- [K8SPXC-1541](https://perconadev.atlassian.net/browse/K8SPXC-1541)
          - Fixed Telemetry module to to consider both empty string \"\" and comma
          separated namespaces in cluster-wide mode\n\n- [K8SPXC-1548](https://perconadev.atlassian.net/browse/K8SPXC-1548)
          Fixed the issue with deleting old backups on Google Cloud Storage by url-decoding
          the object path before deleting it (Thank you Mateusz Gruszkiewicz for reporting
          this issue)\n\n- [K8SPXC-1631](https://perconadev.atlassian.net/browse/K8SPXC-1631)
          - Fixed the issue with the Operator restarting pod-0 after the cluster is
          ready. The issue is caused by ConfigMap and StatefulSet being created too
          close to each other and Kubernetes API can't return the newly created ConfigMap
          before creating the StatefulSet. The issue is fixed by reconciling the StatefulSet
          after the reconciliation of ConfigMap is completed.\n\n- [K8SPXC-1664](https://perconadev.atlassian.net/browse/K8SPXC-1664)
          - Fixed the use of the proper script to check PXC nodes when adding them
          by HAProxy\n\n##### Supported Software\n\nThe Operator was developed and
          tested with the following software:\n\n- Percona XtraDB Cluster versions
          8.4.5-5.1 (Tech preview), 8.0.42-33.1, and 5.7.44-31.65\n- Percona XtraBackup
          versions 8.4.0-3, 8.0.35-34.1, and 2.4.29\n- HAProxy 2.8.15-1\n- ProxySQL
          2.7.3\n- LogCollector based on fluent-bit 4.0.1\n- PMM Client 2.44.1 and
          3.3.1\n\nOther options may also work but have not been tested.\n\n#####
          Supported Platforms\n\nPercona Operators are designed for compatibility
          with all [CNCF-certified](https://www.cncf.io/training/certification/software-conformance/)
          Kubernetes distributions. Our release process includes targeted testing
          and validation on major cloud provider platforms and OpenShift, as detailed
          below for Operator version 1.16.0:\n\n- [Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine)
          1.30 - 1.33\n- [Amazon Elastic Container Service for Kubernetes (EKS)](https://aws.amazon.com)
          1.30 - 1.33\n- [Azure Kubernetes Service (AKS)](https://azure.microsoft.com/en-us/services/kubernetes-service/)
          1.30 - 1.33\n- [OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift)
          4.15 - 4.19\n- [Minikube](https://minikube.sigs.k8s.io/docs/) 1.36.0 based
          on Kubernetes 1.33.1\n\nThis 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.\n\n### [`v1.17.0`](https://redirect.github.com/percona/percona-xtradb-cluster-operator/releases/tag/v1.17.0)\n\n[Compare
          Source](https://redirect.github.com/percona/percona-xtradb-cluster-operator/compare/v1.16.1...v1.17.0)\n\n####
          Release Highlights\n\n##### Improved observability for HAProxy and ProxySQL\n\nGet
          insights into the HAProxy and ProxySQL performance by connecting to their
          statistics pages. Use the `cluster-name-haproxy:8084` and `cluster-name-proxysql:6070`
          endpoints to do so. Learn about other available ports in the [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/haproxy-conf.html).\n\n#####
          Improved cluster load management during backups\n\nIf parallel backups overload
          your cluster, you can turn off parallel execution to prevent this. Previously,
          this meant that you could only run one backup at a time - no new backups
          could start until the current one was finished. Now, the Operator queues
          backups and runs them one after another automatically. You can fine-tune
          the backup sequence by setting the start time for all backups or for a specific
          on-demand one using the [`spec.backup.startingDeadlineSeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#backupstartingdeadlineseconds)
          Custom Resource option. This provides greater control over backup operations.\n\nAnother
          improvement is for the case when your database cluster becomes unhealthy,
          for example, when a Pod crashes or restarts. The Operator suspends running
          backups to reduce the cluster's load. Once the cluster recovers and reports
          a Ready status, the Operator resumes the suspended backup. To further offload
          the cluster during an unhealthy state, you can configure how long a backup
          remains suspended by using the [`spec.backup.suspendedDeadlineSeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#backupsuspendeddeadlineseconds)
          Custom Resource option. If this time expires before the cluster recovers,
          the backup is marked as \"failed.\"\n\n##### Monitor PMM Client health and
          status\n\nPercona Monitoring and Management (PMM) is a great tool to [monitor
          the health of your database cluster](https://docs.percona.com/percona-operator-for-mysql/pxc/monitoring.html).
          Now you can also learn if PMM itself is healthy using probes - a Kubernetes
          diagnostics mechanism to check the health and status of containers. Use
          the [`spec.pmm.readinessProbes.*`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pmmreadinessprobesinitialdelayseconds)
          and [`spec.pmm.livenessProbes.*`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pmmlivenessprobesinitialdelayseconds)
          Custom Resource options to fine-tune Readiness and Liveness probes for PMM
          Client.\n\n##### Improved observability of binary log backups\n\nGet insights
          into the success and failure rates of binlog operations, timeliness of processing
          and uploads and potential gaps or inconsistencies in binlog data with the
          Prometheus metrics added for the Operator. Gather this data by connecting
          to the `<pitr-pod-service>:8080/metrics` endpoint. Learn more about the
          available metrics in the [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/backups-pitr.html#binary-logs-statistics).\n\n####
          Deprecation, Rename and Removal\n\nThe `spec.haproxy.exposePrimary.enabled`
          field is deprecated. If enabled via the `spec.haproxy.enabled`, the HAProxy
          primary service is already exposed.\n\n#### New Features\n\n- [K8SPXC-747](https://perconadev.atlassian.net/browse/K8SPXC-747),
          [K8SPXC-1473](https://perconadev.atlassian.net/browse/K8SPXC-1473) - Add
          the ability to access the statistics pages for HAProxy and ProxySQL\n\n-
          [K8SPXC-1366](https://perconadev.atlassian.net/browse/K8SPXC-1366) - Add
          the ability to queue backups and run them sequentially, and to optimize
          the cluster load with the ability to suspend backups for an unhealthy cluster.
          A user can assign the start time and suspension time to backups to manage
          them better.\n\n- [K8SPXC-1432](https://perconadev.atlassian.net/browse/K8SPXC-1432)
          - Enable users to configure cluster-wide Operator deployments in OpenShift
          certified catalog using OLM.\n\n#### Improvements\n\n- [K8SPXC-1367](https://perconadev.atlassian.net/browse/K8SPXC-1367)
          - Now a user can configure Readiness and Liveness probes for PMM Client
          container to check its health and status\n\n- [K8SPXC-1461](https://perconadev.atlassian.net/browse/K8SPXC-1461)
          - Improve logging for resizing PVC with the information about successful
          and failed PVC resize. Log errors on resize attempts if the Storage Class
          doesn't support resizing.\n\n- [K8SPXC-1466](https://perconadev.atlassian.net/browse/K8SPXC-1466)
          - Mark the containers that provide the service as default ones with the
          annotation. This enables a user to connect to a Pod without explicitly specifying
          a container.\n\n- [K8SPXC-1473](https://perconadev.atlassian.net/browse/K8SPXC-1473)
          - Add the ability to connect to the built-in statistics pages for HAProxy
          and ProxySQL by exposing the ports for those pages\n\n- [K8SPXC-1475](https://perconadev.atlassian.net/browse/K8SPXC-1475)
          - Update the backup image to use AWS CLI instead of MinIO CLI due to the
          license change\n\n- [K8SPXC-1510](https://perconadev.atlassian.net/browse/K8SPXC-1510)
          - Add the ability to suppress messages about the use of deprecated features
          in MySQL Error Log by adding the `log_error_suppression_list` key from the
          `my.cnf` configuration file and defining the message number in the `spec.pxc.configuration`
          subsection of the Custom Resource manifest. See [how to change MySQL options](https://docs.percona.com/percona-operator-for-mysql/pxc/options.html)
          for steps. This improves readability for MySQL error log.\n\n- [K8SPXC-1512](https://perconadev.atlassian.net/browse/K8SPXC-1512)
          - For Percona XtraDB Cluster version 8.4 and above, binary log user defined
          functions for point-in-time recovery (`binlog_utils_udf`) are now installed
          as a component instead of a plugin. This improves their compatibility across
          platforms and provides automatic dependency handling.\n\n- [K8SPXC-1542](https://perconadev.atlassian.net/browse/K8SPXC-1542)
          - Improve binlog upload for large files to Azure blob storage with the ability
          to define the block size and the number of concurrent writers for the upload
          (Thanks to user dcaputo-harmoni for contribution)\n\n- [K8SPXC-1543](https://perconadev.atlassian.net/browse/K8SPXC-1543)
          - Set PITR controller reference for binlog-collector deployment the same
          way as it's set for PXC and proxy StatefulSets. This creates a connection
          between PITR deployment and cluster resource (Thank you Vlad Gusev for the
          contribution)\n\n- [K8SPXC-1544](https://perconadev.atlassian.net/browse/K8SPXC-1544)
          - Improve observability of binlog collector by adding the support of basic
          Prometheus metrics (Thank you Vlad Gusev for the contribution)\n\n- [K8SPXC-1567](https://perconadev.atlassian.net/browse/K8SPXC-1567)
          - N\n\n</details>\n\n---\n\n### Configuration\n\n\U0001F4C5 **Schedule**:
          Branch creation - At any time (no schedule defined), Automerge - At any
          time (no schedule defined).\n\n\U0001F6A6 **Automerge**: Disabled by config.
          Please merge this manually once you are satisfied.\n\n\u267B **Rebasing**:
          Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.\n\n\U0001F47B
          **Immortal**: This PR will be recreated if closed unmerged. Get [config
          help](https://redirect.github.com/renovatebot/renovate/discussions) if that's
          undesired.\n\n---\n\n - [ ] <!-- rebase-check -->If you want to rebase/retry
          this PR, check this box\n\n---\n\nThis PR was generated by [Mend Renovate](https://mend.io/renovate/).
          View the [repository job log](https://developer.mend.io/github/vexxhost/atmosphere).\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4yNjQuMCIsInVwZGF0ZWRJblZlciI6IjQyLjg1LjEiLCJ0YXJnZXRCcmFuY2giOiJzdGFibGUvMjAyMy4xIiwibGFiZWxzIjpbInNraXAtcmVsZWFzZS1ub3RlcyJdfQ==-->\n"
        change_url: https://github.com/vexxhost/atmosphere/pull/2595
        commit_id: 5d635ae7d201989f087661c6356a3703e1026788
        patchset: 5d635ae7d201989f087661c6356a3703e1026788
        project:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/atmosphere
          name: vexxhost/atmosphere
          short_name: atmosphere
        src_dir: src/github.com/vexxhost/atmosphere
        topic: null
      buildset: 2cdabb163e2a4583b78a51ddd1aa586b
      buildset_refs:
      - branch: stable/2023.1
        change: '2595'
        change_message: "Update pxc (stable/2023.1)\n\n> \u2139\uFE0F **Note**\n>
          \n> This PR body was truncated due to platform limits.\n\nThis PR contains
          the following updates:\n\n| Package | Type | Update | Change | [Age](https://docs.renovatebot.com/merge-confidence/)
          | [Confidence](https://docs.renovatebot.com/merge-confidence/) |\n|---|---|---|---|---|---|\n|
          docker.io/percona/haproxy |  | patch | `2.8.14` \u2192 `2.8.18` | ![age](https://developer.mend.io/api/mc/badges/age/docker/docker.io%2fpercona%2fhaproxy/2.8.18?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/docker.io%2fpercona%2fhaproxy/2.8.14/2.8.18?slim=true)
          |\n| docker.io/percona/percona-xtradb-cluster-operator |  | minor | `1.17.0`
          \u2192 `1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/docker/docker.io%2fpercona%2fpercona-xtradb-cluster-operator/1.19.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/docker.io%2fpercona%2fpercona-xtradb-cluster-operator/1.17.0/1.19.0?slim=true)
          |\n| [github.com/percona/percona-xtradb-cluster-operator](https://redirect.github.com/percona/percona-xtradb-cluster-operator)
          | require | minor | `v1.16.1` \u2192 `v1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fpercona%2fpercona-xtradb-cluster-operator/v1.19.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fpercona%2fpercona-xtradb-cluster-operator/v1.16.1/v1.19.0?slim=true)
          |\n| [percona/percona-xtradb-cluster-operator](https://redirect.github.com/percona/percona-xtradb-cluster-operator)
          |  | minor | `1.17.0` \u2192 `1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/github-releases/percona%2fpercona-xtradb-cluster-operator/1.19.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/github-releases/percona%2fpercona-xtradb-cluster-operator/1.17.0/1.19.0?slim=true)
          |\n| [pxc-operator](https://docs.percona.com/percona-operator-for-mysql/pxc/)
          ([source](https://redirect.github.com/percona/percona-helm-charts)) |  |
          minor | `1.17.0` \u2192 `1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/helm/pxc-operator/1.19.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/helm/pxc-operator/1.17.0/1.19.0?slim=true)
          |\n| quay.io/prometheus/mysqld-exporter |  | minor | `v0.17.0` \u2192 `v0.18.0`
          | ![age](https://developer.mend.io/api/mc/badges/age/docker/quay.io%2fprometheus%2fmysqld-exporter/v0.18.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/quay.io%2fprometheus%2fmysqld-exporter/v0.17.0/v0.18.0?slim=true)
          |\n\n---\n\n### Release Notes\n\n<details>\n<summary>percona/percona-xtradb-cluster-operator
          (github.com/percona/percona-xtradb-cluster-operator)</summary>\n\n### [`v1.19.0`](https://redirect.github.com/percona/percona-xtradb-cluster-operator/releases/tag/v1.19.0)\n\n[Compare
          Source](https://redirect.github.com/percona/percona-xtradb-cluster-operator/compare/v1.18.0...v1.19.0)\n\n#####
          Release Highlights\n\nThis release of Percona Operator for MySQL based on
          Percona XtraDB Cluster includes the following new features and improvements:\n\n#####
          Ensure data security for Percona XtraDB Cluster 8.4 with data-at-rest encryption\n\nData
          at rest encryption ensures that sensitive information stored on disk remains
          protected from unauthorized access, even if the physical media is compromised.
          It is a foundational safeguard for compliance, trust and security in modern
          database environments.\n\nThe Operator supports data at rest encryption
          for MySQL 8.0 with HashiCorp Vault using the `keyring_vault` *plugin*. Now,
          it also supports data at rest encryption for MySQL 8.4, leveraging the `keyring_vault`
          *component*.\n\nThis enhancement enables you to benefit from the rich feature
          set of the latest major version of Percona XtraDB Cluster 8.4 while ensuring
          your sensitive data is secured. In doing so, you can meet compliance requirements
          and protect critical information without added operational complexity. Learn
          how to [configure data at rest encryption for Percona XtraDB Cluster 8.4](https://docs.percona.com/percona-operator-for-mysql/pxc/encryption-setup.html).\n\n#####
          Percona XtraDB Cluster 8.4 is now fully supported\n\nPercona XtraDB Cluster
          8.4 is now fully supported and recommended for production deployments. Starting
          with this release, it becomes the default version for all new database cluster
          deployments using the Operator. This support enables you to benefit from
          its latest features, performance improvements, and enhanced security.\n\n#####
          Use your own CA certificates for TLS verification\n\nYou can now use your
          organization\u2019s custom Certificate Authority (CA) to securely verify
          TLS communication with S3 storage during backups and restores.\n\nThe configuration
          is straightforward: create the Secret that stores your custom CA and certificates
          to authorize in the S3 storage. Then reference this Secret and specify the
          CA certificate in the `caBundle` option in the Operator Custom Resource.
          The Operator will verify TLS communication against it.\n\nHere's the example
          configuration:\n\n```yml\nstorages:\n  minio-s3:\n    type: s3\n    verifyTLS:
          true\n    s3:\n      caBundle:\n         name: minio-ca-bundle\n         key:
          tls.crt\n```\n\nWith this improvement, you ensure the following:\n\n- Security
          without compromise \u2013 no more bypassing identity checks.\n- Alignment
          with your internal standards \u2013 use the CA your company already trusts.\n-
          Confidence in backup and restore flows \u2013 every S3 interaction is properly
          verified.\n\nRead more about the use of own CA certificates in our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/backups-storage.html#configure-tls-verification-with-custom-certificates-for-s3-storage)\n\n#####
          Configure duration for certificates issued by cert-manager\n\nBy default,
          the `cert-manager` generates certificates valid for 90 days. You now have
          more control over certificate lifetimes and can configure their custom duration
          when you create a new cluster. This way you can align with your organization's
          security and compliance policies.\n\nUse the following Custom Resource options
          to configure certificate duration:\n\n- `.spec.tls.certValidityDuration`
          \u2013 validity period for generated certificates\n- `.spec.tls.caValidityDuration`
          \u2013 validity period for the Certificate Authority (CA)\n\n```yaml\n  tls:\n
          \   enabled: true\n    certValidityDuration: 2160h\n    caValidityDuration:
          26280h\n```\n\nNote that the Operator enforces minimum durations to certificates:\n\n-
          For TLS certificates \u2013 1 hour\n- For CA certificate \u2013 730 hours.\n\nAlso,
          we don't recommend setting duration to exactly 1 hour to prevent certificate
          generation issues. Read more about rules and limitations about certificate
          duration configuration in our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/tls-cert-manager.html#customize-certificate-duration-for-cert-manager).\n\nThis
          improvement empowers you to fine-tune certificate lifetimes while keeping
          your cluster secure and stable.\n\n##### Security context for ProxySQL sidecar
          containers\n\nYou can now define the security context for ProxySQL sidecar
          containers in the Operator, reducing the risk of unsecured sidecars bypassing
          Pod restrictions. This improvement lets you set user IDs, privileges, and
          filesystem access directly, ensuring compliance and strengthening Pod security.\n\nConfigure
          the security context in your custom resource. For example:\n\n```yaml\nspec:\n
          \ proxysql:\n       sidecars:\n          securityContext:\n              privileged:
          false\n```\n\nWith this change, you enforce safer defaults across your deployments
          and close security gaps at the Pod level.\n\n##### Improved load balancing
          with ProxySQL scheduler (tech preview)\n\nThe Operator now integrates with
          the external `pxc_scheduler_handler` tool to improve query routing. This
          feature is currently in tech preview, so we recommend experimenting with
          it in test or staging environments before using it in production.\n\nWith
          this scheduler you get finer control over how your SQL queries are routed
          within your PXC cluster:\n\n- SELECT queries (that don't use FOR UPDATE)
          are intelligently distributed across all PXC nodes\u2014or all nodes except
          the writer, depending on your settings.\n- Non-SELECT queries and SELECT
          FOR UPDATE statements are routed to the writer node.\n- You don't have to
          micromanage the writer role: the scheduler automatically ensures only one
          writer is active at any time.\n\nThis means you could see:\n\n- better performance
          and higher throughput from distributing query loads\n- greater reliability
          with no single point of failure\n\n* Improved cluster health through early
          detection of replication lag and node issues\n\n- more efficient use of
          your resources and hardware\n- a smoother, more predictable experience for
          everyone using the database\n\nSee our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/proxysql-conf.html#proxysql-scheduler-tech-preview)
          for full information about the scheduler behavior and setup.\n\nThe previous
          internal scheduler remains enabled by default to maintain backward compatibility.
          You can switch to the new one when you're ready to benefit from smarter
          query handling.\n\n##### Customize HAProxy backend health check intervals
          and failover behavior\n\nYou can now control how quickly HAProxy detects
          and reacts to node failures. Instead of waiting the default 20 seconds while
          HAProxy performs the failover, you can tune health checks to cut that down
          to just a few seconds. That means your applications recover faster, and
          users don't get stuck with hanging sessions when a node goes down.\n\nYou
          no longer need to override the entire HAProxy configuration to achieve this
          \u2014 the operator now gives you simple, direct options in the Custom Resource
          specification:\n\n```yaml\nhaproxy:  \n   healthCheck:\n       interval:
          10000\n       rise: 1\n       fall: 2\n```\n\nBy adjusting how often checks
          run and how many failures or successes mark a node as \u201Cdown\u201D or
          \u201Cup,\u201D you get faster failover, cleaner client handling, and easier
          configuration that is safe to upgrade and tailored to your environment.\n\n#####
          Switch from HAProxy to ProxySQL at runtime\n\nYou can now switch from HAProxy
          to ProxySQL without redeploying your Percona XtraDB Cluster. Previously,
          you had to choose ProxySQL only at startup. Now ProxySQL has the `caching_sha2_password`
          as the default authentication plugin, which gives you the flexibility to
          start with HAProxy and migrate to ProxySQL later as your needs evolve.\n\nWith
          this release, ProxySQL also includes a new [scheduler](#improved-load-balancing-with-proxysql-scheduler-tech-preview)
          that enhances SQL awareness, automates read/write splitting, and handles
          failovers more intelligently. This leads to faster queries, increased reliability,
          and more efficient cluster resource usage.\n\n**Which proxy should you choose?**\n\n-
          **HAProxy:** Choose HAProxy if you need a lightweight, TCP-level load balancer
          with minimal configuration. Note that for read/write splitting, your clients
          must connect to different HAProxy ports based on the query type.\n- **ProxySQL:**
          Opt for ProxySQL if you want built-in read/write splitting, advanced query-level
          control, and automated failover logic right out of the box.\n\nEach proxy
          brings its own resource requirements and advantages. We offer [additional
          guidance](https://docs.percona.com/percona-operator-for-mysql/pxc/load-balancing.html#what-load-balancer-to-use)
          on selecting the right proxy for your environment, plus [detailed recommendations](https://docs.percona.com/percona-operator-for-mysql/pxc/proxy-switching.html)
          on resource planning and best practices. Review these carefully to ensure
          your choice fits your operational and performance needs.\n\nTo switch between
          proxies, update your Custom Resource to set `haproxy.enabled` to `false`
          and `proxysql.enabled` to `true`. Apply the changes, and the Operator will
          handle the transition for you by restarting the relevant proxy Pods.\n\nWith
          this improvement you now control your proxy choice at runtime, and ProxySQL
          brings smarter routing and resilience right into the Operator.\n\n#####
          ProxySQL 3 support\n\nYou can now deploy ProxySQL 3 with Percona Operator
          for MySQL. This gives you more flexibility and control over how your applications
          connect to MySQL inside Kubernetes. Here\u2019s what you get:\n\n- Dual\u2011password
          support enables you to introduce a new password while the old one is still
          valid. As a result, you can rotate passwords without downtime\n- Enhanced
          event and query logging gives you real\u2011time visibility into query behavior
          and application traffic.\n- ProxySQL now logs the actual values bound to
          prepared statements. This helps you debug queries more effectively, since
          you see what data was passed instead of just placeholders\n- Event logs
          now include metadata about ProxySQL version and format. This makes it easier
          to track and audit logs across upgrades in your Operator\u2011managed deployments.\n\n#####
          Direct-access backups: Improved performance and reliability with sidecars
          (tech preview)\n\nBy default, the Operator makes backups using the SST method.
          This creates a separate backup Pod with Percona XtraBackup, while the database
          node enters Donor state and stops serving client requests. SST backups can
          also fail with cryptic network errors, making root cause analysis and recovery
          difficult.\n\nStarting with version 1.19.0, you can make backups via the
          XtraBackup sidecar container. The Operator deploys a sidecar with XtraBackup
          inside each Percona XtraDB Cluster Pod. This sidecar makes a backup and
          uploads it to the remote backup storage. The database Pod doesn\u2019t change
          its state to Donor and keeps accepting client requests.\n\nUsing the sidecar
          method provides a direct access to data thus boosting backup performance.
          The sidecar container constantly runs in the database Pod, so you have constant
          access to logs and status, which simplifies troubleshooting.\n\nTo enable
          the XtraBackup sidecar container backup method, set `PXCO_FEATURE_GATES=XtrabackupSidecar=true`
          environment variable in the Operator Deployment.\nThis functionality is
          in the tech preview stage and currently supports only cloud storages. We
          encourage you to try it out in your testing or staging environments and
          leave your feedback.\n\nFuture enhancements such as support of PVC volumes,
          backup encryption and incremental backups are planned for future releases.\n\nTo
          learn more about XtraBackup sidecar container backup method, see our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/backups.html#xtrabackup-sidecar-method-tech-preview).\n\n#####
          Ensure only up to date data is served during backups\n\nWhen a node donates
          data during backups or SST, it enters into the DONOR state. At this point,
          the node should no longer handle client connections. HAProxy's external
          check correctly blocked new connections to the Donor node but allowed existing
          sessions to remain active. Those lingering sessions could return slow or
          outdated results.\n\nThe HAProxy default configuration now includes the
          `on-marked-down shutdown-sessions` directive. As soon as HAProxy marks a
          node as down, all active connections are immediately closed and clients
          reconnect to remaining active nodes. This ensures that only fresh, up to
          date data is served during backups.\n\n##### Automatic cleanup of backup
          and restore Jobs and associated Pods\n\nThe Operator creates a dedicated
          Job and Pod for every backup and restore operation. Previously, these Jobs
          and Pods remained in the cluster even after the operation was finished,
          and you had to manually delete them to free up resources.\n\nNow, you can
          offload this task to the Operator. Specify a time-to-live (TTL) for backup
          and restore Jobs once the operation is finished. When the TTL expires, the
          Operator automatically deletes the Job and its associated Pod.\n\nModify
          your Custom Resource as follows:\n\n```yaml\nbackup:\n  image: perconalab/percona-xtradb-cluster-operator:main-pxc8.0-backup\n
          \ ttlSecondsAfterFinished: 3600\n```\n\nThis setting is global. It applies
          to all on-demand and scheduled backups, and all restores.\n\nThe Operator
          also ensures reliability: if a backup or restore takes longer than the configured
          TTL, it applies the `internal.percona.com/keep-job` finalizer to allow the
          operation to finish. After the operation completes either with the `Succeeded`
          or the `Failed` status, the finalizer is removed and the Job is cleaned
          up.\n\nThis improvement reduces manual maintenance overhead, gives you control
          over the processes lifetime for debugging or auditing purposes and helps
          keep your cluster healthy and efficient. By reducing unnecessary resource
          buildup, you gain smoother operations, lower maintenance overhead and improved
          reliability in production environments.\n\n##### Improved backup identification
          for point-in-time recovery readiness\n\nWhen a backup contains binlog gaps,
          the Operator now creates a `<backup-name>.pitr-not-ready` file in the backup
          storage. This file makes it easy to identify which backups are appropriate
          for point in time recovery both in the storage and when listing backup objects.\n\nBefore
          starting a restore, the Operator checks for this marker file and blocks
          unsafe restores, protecting you from incomplete recovery attempts. If needed,
          you can override this safeguard by adding the `percona.com/unsafe-pitr`
          annotation to the Restore object. Use this override with caution, as this
          is an unsafe configuration.\n\n##### Attach external PVCs for shared data
          access across applications and the database cluster\n\nSometimes your database
          needs more than its own internal storage. For example, it needs access to
          reference files, shared configuration files or lookup tables generated outside
          the database but still essential for queries and procedures.\n\nYou can
          now attach auxiliary pre-existing PVCs and mount that external data directly
          into your database, ProxySQL or HAProxy pods in a clean, declarative way
          using the Custom Resource.\n\nThis example configuration shows how to attach
          external PVC to the XtraDB Cluster Pods:\n\n```yaml\npxc:\n  extraPVCs:\n
          \   - name: extra-data-volume\n      claimName: my-extra-storage\n      mountPath:
          /var/lib/mysql-extra\n      readOnly: false\n```\n\nThis improvement gives
          you a reliable way to separate internal database storage from external domain
          data, update shared datasets independently, and still benefit from the Operator\u2019s
          automation and resilience.\n\n##### Customize password generation by the
          Operator\n\nBy default, the Operator generates user passwords using alphanumeric
          characters plus a set of special symbols. Some tools such as MySQL Prometheus
          Exporter or mysqlsh don't support certain symbols, which can make those
          passwords invalid.\n\nTo improve compatibility and user experience, you
          can now customize password generation parameters in the Custom Resource:\n\n```yaml\nspec:\n
          passwordGenerationOptions:\n   symbols: \"!#$%&()*+,-.<=>?@&#8203;[]^_{}~\"\n
          \  maxLength: 20\n   minLength: 16\n```\n\nThis enhancement lets you keep
          the convenience of automated password generation and at the same time ensure
          compliance with the tools and environments you integrate with the Operator.\n\n#####
          Configure memory allocator in the Operator\n\nBy default, Percona Operator
          for XtraDB Cluster uses the system allocator (`libc`) to manage memory.
          While this works for most cases, alternative allocators such as `jemalloc`
          and `tcmalloc` can improve performance and reduce fragmentation in high-traffic
          workloads.\n\nTo have more flexibility, you can now configure the memory
          allocator directly in the Custom Resource:\n\n```yaml\nspec:\n   pxc:\n
          \    mysqlAllocator: jemalloc\n```\n\nSupported values are:\n\n- `jemalloc`\n-
          `tcmalloc`\n- `libc` (default, used when no value is set)\n\nIf you have
          already configured the memory allocator via the environment variable, the
          Operator will respect that setting and use it instead of the Custom Resource
          value.\n\nThis enhancement lets you fine-tune memory management for your
          cluster while keeping compatibility with existing configurations.\n\n#####
          Deprecation, rename, removal\n\n**Removed in 1.19.0:**\n\n- `proxysql.readinessDelaySec`
          and `proxysql.livenessDelaySec` fields are removed as redundant\n\n**Deprecated
          (will be removed in 1.22.0):**\n\n- `pxc.livenessDelaySec`. Use [`pxc.livenessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pxclivenessprobesinitialdelayseconds)\n-
          `pxc.readinessDelaySec`. Use [`pxc.readinessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pxcreadinessprobesinitialdelayseconds)\n-
          `haproxy.livenessDelaySec`. Use [`haproxy.livenessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#haproxylivenessprobesinitialdelayseconds)\n-
          `haproxy.readinessDelaySec`. Use [`haproxy.readinessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#haproxyreadinessprobesinitialdelayseconds)\n\n#####
          Changelog\n\n##### New Features\n\n- [K8SPXC-1332](https://perconadev.atlassian.net/browse/K8SPXC-1332)
          - Added the ability to load custom SSL certificates for backup operations
          to S3 storage. This enables secure communication with S3-compatible storage
          using the certificates approved and trusted by your company (Thank you Azam
          Abdoelbasier for submitting this request).\n- [K8SPXC-1494](https://perconadev.atlassian.net/browse/K8SPXC-1494)
          - Added the ability to configure the duration of TLS certificates created
          by `cert-manager`. This allows users to customize certificate lifecycles
          to meet their specific security requirements.\n- [K8SPXC-1576](https://perconadev.atlassian.net/browse/K8SPXC-1576)
          - Added the ability to use the XtraBackup sidecar container instead of SST
          for creating backups. This provides an alternative, potentially more efficient
          backup method.\n- [K8SPXC-1688](https://perconadev.atlassian.net/browse/K8SPXC-1688)
          - Added ability to mount pre-existing auxiliary PVCs as volumes to database
          and proxy pods. This facilitates easier integration with external data and
          storage resources (Thank you Emin AKTAS for submitting the request and contributing
          to it).\n- [K8SPXC-1733](https://perconadev.atlassian.net/browse/K8SPXC-1733)
          - Added the ability to customize password generation parameters, such as
          length and character sets via the Custom Resource. This ensures smooth operation
          of the tools with specific requirements towards password and leverages the
          automatic password generation of the Operator (Thank you user fydrah for
          submitting the request and contributing to it).\n- [K8SPXC-1734](https://perconadev.atlassian.net/browse/K8SPXC-1734)
          - Introduced configurable HAProxy backend health check parameters that can
          be tuned without overriding the entire configuration. This simplifies performance
          tuning for high-availability setups (Thank you Tim Stoop for submitting
          the request and contributing to it).\n\n##### Improvements\n\n- [K8SPXC-735](https://perconadev.atlassian.net/browse/K8SPXC-735)
          - Added the support of the `pxc_scheduler_handler` ProxySQL scheduler for
          SQL-aware routing and effective read/write splitting. This allows for better
          utilization of resources by distributing read-only traffic across the entire
          cluster while routing write requests only to the writer node.\n- [K8SPXC-992](https://perconadev.atlassian.net/browse/K8SPXC-992)
          - Improved binlog naming to prevent potential collisions between different
          collectors. The updated naming convention ensures unique and consistent
          identification of binary log files in storage.\n- [K8SPXC-1144](https://perconadev.atlassian.net/browse/K8SPXC-1144)
          - Introduced a mechanism to mark S3 backups as PITR-unready if binlog gaps
          are detected. This prevents users from attempting invalid point-in-time
          recoveries using inconsistent backups.\n- [K8SPXC-1214](https://perconadev.atlassian.net/browse/K8SPXC-1214)
          - Added an option to automatically clean up completed backup and restore
          jobs and their associated pods. This improvement helps reduce pressure on
          the Kubernetes API by removing stale resources (Thank you Alexandre Barth
          for reporting this issue).\n- [K8SPXC-1319](https://perconadev.atlassian.net/browse/K8SPXC-1319)
          - Enhanced the operator to support running multiple backup restores for
          different clusters in parallel. This removes a previous limitation that
          blocked concurrent restore operations across the environment.\n- [K8SPXC-1327](https://perconadev.atlassian.net/browse/K8SPXC-1327)
          - Added the ability to change the memory allocator for MySQL to improve
          memory management efficiency. This change helps optimize the overall memory
          footprint of PXC pods.\n- [K8SPXC-1373](https://perconadev.atlassian.net/browse/K8SPXC-1373)
          - Improved core dump handling to ensure that crashed instances can recover
          more reliably after an SST. This enhancement aids in diagnosing and recovering
          from unexpected server failures.\n- [K8SPXC-1431](https://perconadev.atlassian.net/browse/K8SPXC-1431)
          - Improved the delete-backup finalizer logic to correctly handle the deletion
          of on-demand backup PVCs.\n- [K8SPXC-1470](https://perconadev.atlassian.net/browse/K8SPXC-1470)
          - Added the ability to switch between HAProxy and ProxySQL within an existing
          cluster. This provides users with more flexibility to change their load-balancing
          solution as their needs evolve.\n- [K8SPXC-1511](https://perconadev.atlassian.net/browse/K8SPXC-1511)
          - Added the support of data at rest encryption for Percona XtraDB Cluster
          8.4 via the `keyring vault` component. This change ensures compatibility
          with the latest security architecture of MySQL 8.4.\n- [K8SPXC-1525](https://perconadev.atlassian.net/browse/K8SPXC-1525)
          - Deprecated `pxc.livenessDelaySec` option in favor of more consistent liveness
          probe parameters. The Operator now prioritizes standard probe configurations
          to manage Pod lifecycle.\n- [K8SPXC-1568](https://perconadev.atlassian.net/browse/K8SPXC-1568)
          - Updated the Operator's password generation logic to prevent the '\\*'
          character from being used as the first character. This avoids potential
          issues with certain authentication plugins and command-line tools.\n- [K8SPXC-1594](https://perconadev.atlassian.net/browse/K8SPXC-1594)
          - Improved the database upgrade logic to prevent the controller from being
          blocked during the operation. This ensures that the Operator remains responsive
          to other cluster changes while an upgrade is in progress.\n- [K8SPXC-1628](https://perconadev.atlassian.net/browse/K8SPXC-1628)
          - Added support for `tcmalloc` as an alternative memory allocator in PXC
          images. This gives users additional options to tune and reduce the memory
          footprint of their database workloads.\n- [K8SPXC-1647](https://perconadev.atlassian.net/browse/K8SPXC-1647)
          - Implemented extended exit codes for garbd to provide better diagnostic
          information for different failure scenarios. This helps users identify the
          root cause of SST and joining issues faster.\n- [K8SPXC-1668](https://perconadev.atlassian.net/browse/K8SPXC-1668)
          - Added support for ProxySQL 3, providing users with access to the latest
          features and performance improvements of the load balancer.\n- [K8SPXC-1683](https://perconadev.atlassian.net/browse/K8SPXC-1683)
          - Expanded smart update tests to include PXC 8.4 and PMM 3, ensuring stable
          upgrade paths for the latest versions.\n- [K8SPXC-1703](https://perconadev.atlassian.net/browse/K8SPXC-1703)
          - Added the support of the `generateEmbeddedObjectMeta` option, improving
          the template handling for sidecars and extra PVCs (Thank you Emin AKTAS
          for reporting and contributing to this issue).\n- [K8SPXC-1748](https://perconadev.atlassian.net/browse/K8SPXC-1748)
          - Eliminated runtime CREATE FUNCTION statements in the PITR collector to
          avoid unnecessary Galera TOI (Total Order Isolation) events. This reduces
          the performance impact on the cluster when the PITR sidecar starts or restarts.\n\n#####
          Bugs Fixed\n\n- [K8SPXC-926](https://perconadev.atlassian.net/browse/K8SPXC-926)
          - Fixed an issue where a failed smart update on one cluster could block
          the Operator from managing other clusters in multi-cluster environments.
          The controller now handles update failures more gracefully without impacting
          independent resources.\n- [K8SPXC-1379](https://perconadev.atlassian.net/browse/K8SPXC-1379)
          - Fixed an issue where monit container resource values in ProxySQL pods
          did not correctly reflect the values specified in the PXC cluster definition.
          The operator now ensures that ProxySQL resource attributes are properly
          applied to the monitoring sidecar containers.\n- [K8SPXC-1424](https://perconadev.atlassian.net/browse/K8SPXC-1424)
          - Resolved a certificate renewal issue where CA certificates in TLS secrets
          could expire before server certificates were renewed. The Operator logic
          was updated to align renewal intervals for CA and server certificates when
          using cert-manager.\n- [K8SPXC-1581](https://perconadev.atlassian.net/browse/K8SPXC-1581)
          - Corrected the order of options in the restore prepare job to ensure that
          `--defaults-file` is passed as the first option to xtrabackup. This fix
          ensures that custom configuration files are correctly prioritized during
          the restore process.\n- [K8SPXC-1617](https://perconadev.atlassian.net/browse/K8SPXC-1617)
          - Fixed a binlog gap issue in Point-in-Time Recovery (PITR) that caused
          repeated test failures. Users are now advised to perform a full backup after
          each PITR restore to ensure data consistency and prevent gaps.\n- [K8SPXC-1632](https://perconadev.atlassian.net/browse/K8SPXC-1632)
          - Added missing SecurityContext configurations for ProxySQL sidecar containers
          to enhance pod security. This change ensures that all sidecars follow the
          defined security standards of the cluster.\n- [K8SPXC-1655](https://perconadev.atlassian.net/browse/K8SPXC-1655)
          - Fixed a failure in xtrabackup when using LZ4 compression on RHEL9-based
          Percona XtraDB Cluster images. The fix addresses compatibility issues with
          the latest compression libraries in the operating system environment.\n-
          [K8SPXC-1686](https://perconadev.atlassian.net/browse/K8SPXC-1686) - Improved
          backup error handling to ensure that providing an invalid Percona XtraBackup
          image results in a failed status. A new timeout field was introduced to
          prevent backup objects from hanging indefinitely in a starting state.\n-
          [K8SPXC-1687](https://perconadev.atlassian.net/browse/K8SPXC-1687) - Fixed
          the `copy-backup.sh` script to correctly handle and copy cloud-based backups
          stored in S3 or Azure. This ensures that the utility script works consistently
          across all supported storage types.\n- [K8SPXC-1701](https://perconadev.atlassian.net/browse/K8SPXC-1701)
          - Ensured that MySQL configurations are correctly mounted to the restore
          prepare job. This fix allows the restore process to use custom MySQL settings
          defined in the cluster (Thank you Emin AKTAS for reporting and contributing
          to this issue).\n- [K8SPXC-1702](https://perconadev.atlassian.net/browse/K8SPXC-1702)
          - Added the ability to override time zones for backup jobs. This resolves
          issues where time-dependent operations could fail due to missing timezone
          definitions (Thank you Emin AKTAS for reporting and contributing to this
          issue).\n- [K8SPXC-1721](https://perconadev.atlassian.net/browse/K8SPXC-1721)
          - Added a sleep interval to the recovery loop to prevent high CPU usage
          spikes when containers restart.\n- [K8SPXC-1725](https://perconadev.atlassian.net/browse/K8SPXC-1725)
          - Fixed a condition where a cluster could return stalled data during a backup
          or SST operation by adding the on-marked-down shutdown-sessions directive
          to HAProxy default configuration. This ensures that only fresh, up to date
          data is served during backups.\n- [K8SPXC-1726](https://perconadev.atlassian.net/browse/K8SPXC-1726)
          - Resolved a deployment breakage in the Operator version 1.18.0 via Helm
          caused by PMM 3 client incompatibilities. The fix ensures a smoother upgrade
          path for users migrating to newer versions of PMM (Thank you Antonio Falzarano
          for reporting and contributing to this issue).\n- [K8SPXC-1760](https://perconadev.atlassian.net/browse/K8SPXC-1760)
          - Fixed the handling of the crVersion field in the Helm chart templates.
          The Operator now correctly considers the version defined in `values.yaml`
          when generating the cluster configuration.\n- [K8SPXC-1771](https://perconadev.atlassian.net/browse/K8SPXC-1771)
          - Fixed the issue with excessive logging by the backup controller when backups
          are suspended or resumed due to an unready cluster. This improves log readability
          and reduces unnecessary diagnostic noise.\n- [K8SPXC-1772](https://perconadev.atlassian.net/browse/K8SPXC-1772)
          - Fixed a state transition bug where unsuspended backups could move directly
          from 'Starting' to 'Succeeded' without entering the 'Running' state. This
          ensures accurate tracking and visibility of the backup process status.\n\n#####
          Documentation Improvements\n\n- [K8SPXC-1747](https://perconadev.atlassian.net/browse/K8SPXC-1747)
          - Improved the documentation with the information about available environment
          variables for cluster components and the Operator. Documented the `S3_WORKERS_LIMIT`
          environment variable to allow throttling of backup deletions.\n- [K8SPXC-1661](https://perconadev.atlassian.net/browse/K8SPXC-1661)
          - Updated the operator documentation to reflect that PMM 3 uses service
          accounts instead of API keys. This ensures that users can correctly configure
          monitoring integration with the latest versions of PMM.\n- [K8SPXC-1663](https://perconadev.atlassian.net/browse/K8SPXC-1663)
          - Improved documentation for Point-in-Time Recovery steps. The updated documentation
          properly separates and sequences the recovery instructions for improved
          readability.\n\n##### Supported Software\n\nThe Operator was developed and
          tested with the following software:\n\n- Percona XtraDB Cluster versions
          8.4.7-7.1, 8.0.44-35.1, and 5.7.44-31.65\n- Percona XtraBackup versions
          8.4.0-5.1, 8.0.35-34.1, and 2.4.29\n- HAProxy 2.8.17\n- ProxySQL 2.7.3-1.2,
          3.0.1-1.2\n- LogCollector based on fluent-bit 4.0.1-1\n- PMM Client 2.44.1-1
          and 3.5.0\n\nOther options may also work but have not been tested.\n\n#####
          Supported Platforms\n\nPercona Operators are designed for compatibility
          with all [CNCF-certified](https://www.cncf.io/training/certification/software-conformance/)
          Kubernetes distributions. Our release process includes targeted testing
          and validation on major cloud provider platforms and OpenShift, as detailed
          below:\n\n- [Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine)
          1.31 - 1.33\n- [Amazon Elastic Container Service for Kubernetes (EKS)](https://aws.amazon.com)
          1.32 - 1.34\n- [Azure Kubernetes Service (AKS)](https://azure.microsoft.com/en-us/services/kubernetes-service/)
          1.32 - 1.34\n- [OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift)
          4.17 - 4.20\n- [Minikube](https://minikube.sigs.k8s.io/docs/) 1.37.0 based
          on Kubernetes 1.34.0\n\nThis 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.\n\n### [`v1.18.0`](https://redirect.github.com/percona/percona-xtradb-cluster-operator/releases/tag/v1.18.0)\n\n[Compare
          Source](https://redirect.github.com/percona/percona-xtradb-cluster-operator/compare/v1.17.0...v1.18.0)\n\n#####
          Release Highlights\n\nThis release of Percona Operator for MySQL based on
          Percona XtraDB Cluster includes the following new features and improvements:\n\n#####
          PMM3 support\n\nThe Operator is natively integrated with [PMM 3](https://www.percona.com/doc/percona-monitoring-and-management/3/index.html),
          enabling you to monitor the health and performance of your Percona Distribution
          for MySQL deployment and at the same time enjoy enhanced performance, new
          features, and improved security that PMM 3 provides.\n\nNote that the Operator
          supports both PMM2 and PMM3. The decision on what PMM version is used depends
          on the authentication method you provide in the Operator configuration:
          PMM2 uses API keys while PMM3 uses service account token. If the Operator
          configuration contains both authentication methods with non-empty values,
          PMM3 takes the priority.\n\nTo use PMM, ensure that the PMM client image
          is compatible with the PMM Server version. Check [Percona certified images](https://docs.percona.com/percona-operator-for-mysql/pxc/images.html)
          for the correct client image.\n\nFor how to configure monitoring with PMM,
          see the [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/monitoring.html).\n\n#####
          Improved monitoring for clusters in multi-region or multi-namespace deployments
          in PMM\n\nNow you can define a custom name for your clusters deployed in
          different data centers. This name helps Percona Management and Monitoring
          (PMM) Server to correctly recognize clusters as connected and monitor them
          as one deployment. Similarly, PMM Server identifies clusters deployed with
          the same names in different namespaces as separate ones and correctly displays
          performance metrics for you on dashboards.\n\nTo assign a custom name, define
          this configuration in the Custom Resource manifest for your cluster:\n\n```yaml\nspec:\n
          \ pmm:\n    customClusterName: testClusterName\n```\n\n##### More resilient
          database restores without matching user Secrets\n\nYou no longer need matching
          user Secrets between your backup and your target cluster to perform a restore.
          The Operator now has a post-restore step that changes user passwords in
          the restored database to the ones from the local Secret. Also, it creates
          missing system users and adds missing grants.\n\nThis flow is the same regardless
          of whether you restore to the same cluster or to a completely new one.\n\nThe
          removal of this major roadblock to have a Secret for restores makes your
          disaster recovery process smoother and more reliable. This enhancement makes
          managing databases on Kubernetes more robust and operator-friendly.\n\n#####
          Improved backup retention for streamlined management of scheduled backups
          in cloud storage\n\nA new backup retention configuration gives you more
          control over how backups are managed in storage and retained in Kubernetes.\n\nWith
          the `deleteFromStorage` flag , you can disable automatic deletion from AWS
          S3 or Azure Blob storage and instead rely on native cloud lifecycle policies.
          This makes backup cleanup more efficient and better aligned with flexible
          storage strategies.\n\nThe legacy `keep` option is now deprecated and mapped
          to the new `retention` block for compatibility. We encourage you to start
          using the `backup.schedule.retention` configuration:\n\n```yaml\nschedule:\n
          \ - name: \"sat-night-backup\"\n    schedule: \"0 0 * * 6\"\n    retention:\n
          \     count: 3\n      type: count\n      deleteFromStorage: true\n    storageName:
          s3-us-west\n```\n\nNote that if you have both `backup.schedule.keep`  and
          `backup.schedule.retention`  defined, the `backup.schedule.retention` takes
          precedence.\n\n##### Added labels to identify the version of the Operator\n\nCustom
          Resource Definition (CRD) is compatible with the last three Operator versions.
          To know which Operator version is attached to it, we've added labels to
          all Custom Resource Definitions. The labels help you identify the current
          Operator version and decide if you need to update the CRD. To view the labels,
          run: `kubectl get crd perconaxtradbclusters.pxc.percona.com --show-labels`.\n\n#####
          Cross-site replication is now supported for Percona XtraDB Cluster 8.4\n\nCross-site
          replication is now available with Percona XtraDB Cluster 8.4.x, lifting
          one of the  limitations in the Operator for this database version. This
          enhancement marks a significant step toward general availability of Percona
          XtraDB Cluster 8.4 in the Operator by enabling multi-site deployments and
          improving resilience across distributed environments.\n\n##### Deprecation,
          Rename and Removal\n\n- The `pxc.expose.loadBalancerIP`, `haproxy.exposePrimary.loadBalancerIP`,
          `haproxy.exposeReplicas.loadBalancerIP` and `proxysql.expose.loadBalancerIP`
          keys are deprecated. The `loadBalancerIP` field is also deprecated upstream
          in Kubernetes\n  due to its inconsistent behavior across cloud providers
          and lack of dual-stack support. As a result, its usage is strongly discouraged.\n\n
          \ We recommend using cloud provider-specific annotations instead, as they
          offer more predictable and portable behavior for managing load balancer
          IP assignments.\n\n  The `pxc.expose.loadBalancerIP`, `haproxy.exposePrimary.loadBalancerIP`,
          `haproxy.exposeReplicas.loadBalancerIP` and `proxysql.expose.loadBalancerIP`
          keys are scheduled for removal in future releases.\n\n- The `backup.schedule.keep`
          field is deprecated and will be removed after release 1.21.0. We recommend
          using the `backup.schedule.retention` instead as follows:\n\n  ```yaml\n
          \ schedule:\n    - name: \"sat-night-backup\"\n      schedule: \"0 0 **
          6\"\n      retention:\n        count: 3\n        type: count\n        deleteFromStorage:
          true\n      storageName: s3-us-west\n  ```\n\n- New repositories for Percona
          XtraBackup and Logcollector\n\n  Now the Operator uses the official Percona
          Docker images for the `percona-xtrabackup` and `logcollector` components.
          Pay attention to the new image repositories when you upgrade the Operator
          and the database. Check the [Percona certified images](https://docs.percona.com/percona-operator-for-mysql/pxc/images.html)
          for exact image names.\n\n- Changes for Helm charts:\n\n  - PMM3 is now
          the default. To keep using PMM2, set the `pmm.tag: 2.44.1`\n  - If you install
          or upgrade the Operator with default manifests using Helm charts on Openshift
          4.19, you must use the `docker.io` registry prefix to guarantee successful
          download from the DockerHub `percona-xtradb-cluster` repository. Read the
          [Considerations for using OpenShift 4.19](#considerations-for-using-openshift-419)
          section for more information.\n\n##### Known limitations\n\n##### Considerations
          for using OpenShift 4.19\n\nStarting with OpenShift 4.19, the way images
          with not fully qualified names are pulled has changed for repositories that
          share the same repository name on DockerHub and Red Hat Marketplace. By
          default the tags are pulled from Red Hat Marketplace. Specifying not fully
          qualified image names may result in the `ImagePullBackOff` error.\n\n- **OLM
          installation:** Images are provided with the fully qualified names and are
          pulled from the Red Hat Marketplace/DockerHub registry.\n- **Manual install/update
          with default manifests:** Images must use the `docker.io` registry prefix
          to guarantee successful download from the Dockerhub `percona-xtradb-cluster`
          repository.\n\nSee our documentation for [manual installation](https://docs.percona.com/percona-operator-for-mysql/pxc/openshift.html#install-the-operator-via-the-command-line-interface)
          or [update](https://docs.percona.com/percona-operator-for-mysql/pxc/update_openshift.html#update-via-the-command-line-interface).\n\n#####
          Changleog\n\n##### New Features\n\n- [K8SPXC-1284](https://perconadev.atlassian.net/browse/K8SPXC-1284)
          - Add the ability to configure protocol for peer-list DNS SRV lookups\n\n-
          [K8SPXC-1599](https://perconadev.atlassian.net/browse/K8SPXC-1599) - Allowed
          setting `loadBalancerClass` service type and using a custom implementation
          of a load balancer rather than the cloud provider default one\n\n##### Improvements\n\n-
          [K8SPXC-1375](https://perconadev.atlassian.net/browse/K8SPXC-1375) - Added
          a new retention configuration to allow users to delegate backup cleanup
          to cloud lifecycle policies (Thank you user Tristan for reporting this issue)\n\n-
          [K8SPXC-1376](https://perconadev.atlassian.net/browse/K8SPXC-1376) - Added
          the ability to restore from backup without a matching Secret resource\n\n-
          [K8SPXC-1399](https://perconadev.atlassian.net/browse/K8SPXC-1399) - Added
          a documentation how to set up a disaster recovery system and transfer workloads
          between sites\n\n- [K8SPXC-1415](https://perconadev.atlassian.net/browse/K8SPXC-1415)
          - Updated the `percona-xtrabackup` image to use the official `percona-xtrabackup`
          Docker image\n\n- [K8SPXC-1430](https://perconadev.atlassian.net/browse/K8SPXC-1430)
          - Improved handling of autogenerated certificates depending on the `delete-ssl`
          finalizer configuration\n\n- [K8SPXC-1448](https://perconadev.atlassian.net/browse/K8SPXC-1448),
          [K8SPXC-1449](https://perconadev.atlassian.net/browse/K8SPXC-1449) - Improved
          the `pvc-resize` test by using a custom storage class for EKS, reducing
          errors and improving the quota handling during resize\n\n- [K8SPXC-1450](https://perconadev.atlassian.net/browse/K8SPXC-1450)
          - Improved PVC resizing behavior when reducing the storage size by reverting
          the values when the quota is reached\n\n- [K8SPXC-1472](https://perconadev.atlassian.net/browse/K8SPXC-1472)
          - Deprecated the `loadBalancerIP` field due to its deprecation upstream\n\n-
          [K8SPXC-1513](https://perconadev.atlassian.net/browse/K8SPXC-1513) - Added
          PXC 8.4 support for version service\n\n- [K8SPXC-1529](https://perconadev.atlassian.net/browse/K8SPXC-1529)
          - Added support for cross-site replication with MySQL 8.4.0 by adding the
          use of `authentication_policy` instead of `default_authentication_plugin`\n\n-
          [K8SPXC-1553](https://perconadev.atlassian.net/browse/K8SPXC-1553) - Added
          support for PMM v3\n\n- [K8SPXC-1560](https://perconadev.atlassian.net/browse/K8SPXC-1560)
          - Added the warning about CRDs not being upgraded automatically after helm
          upgrade to the output\n\n- [K8SPXC-1566](https://perconadev.atlassian.net/browse/K8SPXC-1566)
          - Improved reconciliation of replicationChannels without proxy Pods by starting
          the database Pod bypassing the proxy (Thank you Justin Reasoner for contributing
          to this issue)\n\n- [K8SPXC-1569](https://perconadev.atlassian.net/browse/K8SPXC-1569)
          - Added Labels for Custom Resource Definitions (CRD) to identify the Operator
          version attached to them\n\n- [K8SPXC-1597](https://perconadev.atlassian.net/browse/K8SPXC-1597)
          - Improve the scheduled backups behavior for a cluster in an unhealthy state
          by postponing the job until the cluster reports the healthy status\n\n-
          [K8SPXC-1605](https://perconadev.atlassian.net/browse/K8SPXC-1605) - Introduced
          Azure CLI for checking if backup objects/folders exist in Azure storage\n\n-
          [K8SPXC-1612](https://perconadev.atlassian.net/browse/K8SPXC-1612) - Added
          the `imagePullSecrets` for PMM image\n\n- [K8SPXC-1615](https://perconadev.atlassian.net/browse/K8SPXC-1615)
          - Added the ability to define a custom cluster name for `pmm-admin` component\n\n-
          [K8SPXC-1624](https://perconadev.atlassian.net/browse/K8SPXC-1624) - Deleted
          deprecated finalizers code\n\n- [K8SPXC-1669](https://perconadev.atlassian.net/browse/K8SPXC-1669)
          - Improve the backup flow by generating a default endpoint URL for a storage
          from a region if it is not provided (Thank you Bernard Grymonpon for reporting
          this issue)\n\n- [K8SPXC-1677](https://perconadev.atlassian.net/browse/K8SPXC-1677)
          - Document the changed behavior with pulling images for default manifests
          on OpenShift 4.19 and update install and update instructions\n\n##### Bugs
          Fixed\n\n- [K8SPXC-1312](https://perconadev.atlassian.net/browse/K8SPXC-1312)
          - Fixed the issue with labels not being updated automatically for point-in-time
          recovery deployment upon Custom Resource changes\n\n- [K8SPXC-1347](https://perconadev.atlassian.net/browse/K8SPXC-1347)
          - Fixed the issue with point-in-time recovery failing due to TLS configuration
          mismatch between the server and the point-in-time recovery job by configuring
          it to use TLS if is required by the server.\n\n- [K8SPXC-1382](https://perconadev.atlassian.net/browse/K8SPXC-1382)
          - Fixed the issue with backup failing on AWS if using IAM profile without
          credentialsSecret by using credentialsSecret only when explicitly specified
          and relying on IAM roles instead (Thank you Itiel Olenick for reporting
          this issue)\n\n- [K8SPXC-1541](https://perconadev.atlassian.net/browse/K8SPXC-1541)
          - Fixed Telemetry module to to consider both empty string \"\" and comma
          separated namespaces in cluster-wide mode\n\n- [K8SPXC-1548](https://perconadev.atlassian.net/browse/K8SPXC-1548)
          Fixed the issue with deleting old backups on Google Cloud Storage by url-decoding
          the object path before deleting it (Thank you Mateusz Gruszkiewicz for reporting
          this issue)\n\n- [K8SPXC-1631](https://perconadev.atlassian.net/browse/K8SPXC-1631)
          - Fixed the issue with the Operator restarting pod-0 after the cluster is
          ready. The issue is caused by ConfigMap and StatefulSet being created too
          close to each other and Kubernetes API can't return the newly created ConfigMap
          before creating the StatefulSet. The issue is fixed by reconciling the StatefulSet
          after the reconciliation of ConfigMap is completed.\n\n- [K8SPXC-1664](https://perconadev.atlassian.net/browse/K8SPXC-1664)
          - Fixed the use of the proper script to check PXC nodes when adding them
          by HAProxy\n\n##### Supported Software\n\nThe Operator was developed and
          tested with the following software:\n\n- Percona XtraDB Cluster versions
          8.4.5-5.1 (Tech preview), 8.0.42-33.1, and 5.7.44-31.65\n- Percona XtraBackup
          versions 8.4.0-3, 8.0.35-34.1, and 2.4.29\n- HAProxy 2.8.15-1\n- ProxySQL
          2.7.3\n- LogCollector based on fluent-bit 4.0.1\n- PMM Client 2.44.1 and
          3.3.1\n\nOther options may also work but have not been tested.\n\n#####
          Supported Platforms\n\nPercona Operators are designed for compatibility
          with all [CNCF-certified](https://www.cncf.io/training/certification/software-conformance/)
          Kubernetes distributions. Our release process includes targeted testing
          and validation on major cloud provider platforms and OpenShift, as detailed
          below for Operator version 1.16.0:\n\n- [Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine)
          1.30 - 1.33\n- [Amazon Elastic Container Service for Kubernetes (EKS)](https://aws.amazon.com)
          1.30 - 1.33\n- [Azure Kubernetes Service (AKS)](https://azure.microsoft.com/en-us/services/kubernetes-service/)
          1.30 - 1.33\n- [OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift)
          4.15 - 4.19\n- [Minikube](https://minikube.sigs.k8s.io/docs/) 1.36.0 based
          on Kubernetes 1.33.1\n\nThis 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.\n\n### [`v1.17.0`](https://redirect.github.com/percona/percona-xtradb-cluster-operator/releases/tag/v1.17.0)\n\n[Compare
          Source](https://redirect.github.com/percona/percona-xtradb-cluster-operator/compare/v1.16.1...v1.17.0)\n\n####
          Release Highlights\n\n##### Improved observability for HAProxy and ProxySQL\n\nGet
          insights into the HAProxy and ProxySQL performance by connecting to their
          statistics pages. Use the `cluster-name-haproxy:8084` and `cluster-name-proxysql:6070`
          endpoints to do so. Learn about other available ports in the [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/haproxy-conf.html).\n\n#####
          Improved cluster load management during backups\n\nIf parallel backups overload
          your cluster, you can turn off parallel execution to prevent this. Previously,
          this meant that you could only run one backup at a time - no new backups
          could start until the current one was finished. Now, the Operator queues
          backups and runs them one after another automatically. You can fine-tune
          the backup sequence by setting the start time for all backups or for a specific
          on-demand one using the [`spec.backup.startingDeadlineSeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#backupstartingdeadlineseconds)
          Custom Resource option. This provides greater control over backup operations.\n\nAnother
          improvement is for the case when your database cluster becomes unhealthy,
          for example, when a Pod crashes or restarts. The Operator suspends running
          backups to reduce the cluster's load. Once the cluster recovers and reports
          a Ready status, the Operator resumes the suspended backup. To further offload
          the cluster during an unhealthy state, you can configure how long a backup
          remains suspended by using the [`spec.backup.suspendedDeadlineSeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#backupsuspendeddeadlineseconds)
          Custom Resource option. If this time expires before the cluster recovers,
          the backup is marked as \"failed.\"\n\n##### Monitor PMM Client health and
          status\n\nPercona Monitoring and Management (PMM) is a great tool to [monitor
          the health of your database cluster](https://docs.percona.com/percona-operator-for-mysql/pxc/monitoring.html).
          Now you can also learn if PMM itself is healthy using probes - a Kubernetes
          diagnostics mechanism to check the health and status of containers. Use
          the [`spec.pmm.readinessProbes.*`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pmmreadinessprobesinitialdelayseconds)
          and [`spec.pmm.livenessProbes.*`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pmmlivenessprobesinitialdelayseconds)
          Custom Resource options to fine-tune Readiness and Liveness probes for PMM
          Client.\n\n##### Improved observability of binary log backups\n\nGet insights
          into the success and failure rates of binlog operations, timeliness of processing
          and uploads and potential gaps or inconsistencies in binlog data with the
          Prometheus metrics added for the Operator. Gather this data by connecting
          to the `<pitr-pod-service>:8080/metrics` endpoint. Learn more about the
          available metrics in the [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/backups-pitr.html#binary-logs-statistics).\n\n####
          Deprecation, Rename and Removal\n\nThe `spec.haproxy.exposePrimary.enabled`
          field is deprecated. If enabled via the `spec.haproxy.enabled`, the HAProxy
          primary service is already exposed.\n\n#### New Features\n\n- [K8SPXC-747](https://perconadev.atlassian.net/browse/K8SPXC-747),
          [K8SPXC-1473](https://perconadev.atlassian.net/browse/K8SPXC-1473) - Add
          the ability to access the statistics pages for HAProxy and ProxySQL\n\n-
          [K8SPXC-1366](https://perconadev.atlassian.net/browse/K8SPXC-1366) - Add
          the ability to queue backups and run them sequentially, and to optimize
          the cluster load with the ability to suspend backups for an unhealthy cluster.
          A user can assign the start time and suspension time to backups to manage
          them better.\n\n- [K8SPXC-1432](https://perconadev.atlassian.net/browse/K8SPXC-1432)
          - Enable users to configure cluster-wide Operator deployments in OpenShift
          certified catalog using OLM.\n\n#### Improvements\n\n- [K8SPXC-1367](https://perconadev.atlassian.net/browse/K8SPXC-1367)
          - Now a user can configure Readiness and Liveness probes for PMM Client
          container to check its health and status\n\n- [K8SPXC-1461](https://perconadev.atlassian.net/browse/K8SPXC-1461)
          - Improve logging for resizing PVC with the information about successful
          and failed PVC resize. Log errors on resize attempts if the Storage Class
          doesn't support resizing.\n\n- [K8SPXC-1466](https://perconadev.atlassian.net/browse/K8SPXC-1466)
          - Mark the containers that provide the service as default ones with the
          annotation. This enables a user to connect to a Pod without explicitly specifying
          a container.\n\n- [K8SPXC-1473](https://perconadev.atlassian.net/browse/K8SPXC-1473)
          - Add the ability to connect to the built-in statistics pages for HAProxy
          and ProxySQL by exposing the ports for those pages\n\n- [K8SPXC-1475](https://perconadev.atlassian.net/browse/K8SPXC-1475)
          - Update the backup image to use AWS CLI instead of MinIO CLI due to the
          license change\n\n- [K8SPXC-1510](https://perconadev.atlassian.net/browse/K8SPXC-1510)
          - Add the ability to suppress messages about the use of deprecated features
          in MySQL Error Log by adding the `log_error_suppression_list` key from the
          `my.cnf` configuration file and defining the message number in the `spec.pxc.configuration`
          subsection of the Custom Resource manifest. See [how to change MySQL options](https://docs.percona.com/percona-operator-for-mysql/pxc/options.html)
          for steps. This improves readability for MySQL error log.\n\n- [K8SPXC-1512](https://perconadev.atlassian.net/browse/K8SPXC-1512)
          - For Percona XtraDB Cluster version 8.4 and above, binary log user defined
          functions for point-in-time recovery (`binlog_utils_udf`) are now installed
          as a component instead of a plugin. This improves their compatibility across
          platforms and provides automatic dependency handling.\n\n- [K8SPXC-1542](https://perconadev.atlassian.net/browse/K8SPXC-1542)
          - Improve binlog upload for large files to Azure blob storage with the ability
          to define the block size and the number of concurrent writers for the upload
          (Thanks to user dcaputo-harmoni for contribution)\n\n- [K8SPXC-1543](https://perconadev.atlassian.net/browse/K8SPXC-1543)
          - Set PITR controller reference for binlog-collector deployment the same
          way as it's set for PXC and proxy StatefulSets. This creates a connection
          between PITR deployment and cluster resource (Thank you Vlad Gusev for the
          contribution)\n\n- [K8SPXC-1544](https://perconadev.atlassian.net/browse/K8SPXC-1544)
          - Improve observability of binlog collector by adding the support of basic
          Prometheus metrics (Thank you Vlad Gusev for the contribution)\n\n- [K8SPXC-1567](https://perconadev.atlassian.net/browse/K8SPXC-1567)
          - N\n\n</details>\n\n---\n\n### Configuration\n\n\U0001F4C5 **Schedule**:
          Branch creation - At any time (no schedule defined), Automerge - At any
          time (no schedule defined).\n\n\U0001F6A6 **Automerge**: Disabled by config.
          Please merge this manually once you are satisfied.\n\n\u267B **Rebasing**:
          Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.\n\n\U0001F47B
          **Immortal**: This PR will be recreated if closed unmerged. Get [config
          help](https://redirect.github.com/renovatebot/renovate/discussions) if that's
          undesired.\n\n---\n\n - [ ] <!-- rebase-check -->If you want to rebase/retry
          this PR, check this box\n\n---\n\nThis PR was generated by [Mend Renovate](https://mend.io/renovate/).
          View the [repository job log](https://developer.mend.io/github/vexxhost/atmosphere).\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4yNjQuMCIsInVwZGF0ZWRJblZlciI6IjQyLjg1LjEiLCJ0YXJnZXRCcmFuY2giOiJzdGFibGUvMjAyMy4xIiwibGFiZWxzIjpbInNraXAtcmVsZWFzZS1ub3RlcyJdfQ==-->\n"
        change_url: https://github.com/vexxhost/atmosphere/pull/2595
        commit_id: 5d635ae7d201989f087661c6356a3703e1026788
        patchset: 5d635ae7d201989f087661c6356a3703e1026788
        project:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/atmosphere
          name: vexxhost/atmosphere
          short_name: atmosphere
        src_dir: src/github.com/vexxhost/atmosphere
        topic: null
      change: '2595'
      change_message: "Update pxc (stable/2023.1)\n\n> \u2139\uFE0F **Note**\n> \n>
        This PR body was truncated due to platform limits.\n\nThis PR contains the
        following updates:\n\n| Package | Type | Update | Change | [Age](https://docs.renovatebot.com/merge-confidence/)
        | [Confidence](https://docs.renovatebot.com/merge-confidence/) |\n|---|---|---|---|---|---|\n|
        docker.io/percona/haproxy |  | patch | `2.8.14` \u2192 `2.8.18` | ![age](https://developer.mend.io/api/mc/badges/age/docker/docker.io%2fpercona%2fhaproxy/2.8.18?slim=true)
        | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/docker.io%2fpercona%2fhaproxy/2.8.14/2.8.18?slim=true)
        |\n| docker.io/percona/percona-xtradb-cluster-operator |  | minor | `1.17.0`
        \u2192 `1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/docker/docker.io%2fpercona%2fpercona-xtradb-cluster-operator/1.19.0?slim=true)
        | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/docker.io%2fpercona%2fpercona-xtradb-cluster-operator/1.17.0/1.19.0?slim=true)
        |\n| [github.com/percona/percona-xtradb-cluster-operator](https://redirect.github.com/percona/percona-xtradb-cluster-operator)
        | require | minor | `v1.16.1` \u2192 `v1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fpercona%2fpercona-xtradb-cluster-operator/v1.19.0?slim=true)
        | ![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fpercona%2fpercona-xtradb-cluster-operator/v1.16.1/v1.19.0?slim=true)
        |\n| [percona/percona-xtradb-cluster-operator](https://redirect.github.com/percona/percona-xtradb-cluster-operator)
        |  | minor | `1.17.0` \u2192 `1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/github-releases/percona%2fpercona-xtradb-cluster-operator/1.19.0?slim=true)
        | ![confidence](https://developer.mend.io/api/mc/badges/confidence/github-releases/percona%2fpercona-xtradb-cluster-operator/1.17.0/1.19.0?slim=true)
        |\n| [pxc-operator](https://docs.percona.com/percona-operator-for-mysql/pxc/)
        ([source](https://redirect.github.com/percona/percona-helm-charts)) |  | minor
        | `1.17.0` \u2192 `1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/helm/pxc-operator/1.19.0?slim=true)
        | ![confidence](https://developer.mend.io/api/mc/badges/confidence/helm/pxc-operator/1.17.0/1.19.0?slim=true)
        |\n| quay.io/prometheus/mysqld-exporter |  | minor | `v0.17.0` \u2192 `v0.18.0`
        | ![age](https://developer.mend.io/api/mc/badges/age/docker/quay.io%2fprometheus%2fmysqld-exporter/v0.18.0?slim=true)
        | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/quay.io%2fprometheus%2fmysqld-exporter/v0.17.0/v0.18.0?slim=true)
        |\n\n---\n\n### Release Notes\n\n<details>\n<summary>percona/percona-xtradb-cluster-operator
        (github.com/percona/percona-xtradb-cluster-operator)</summary>\n\n### [`v1.19.0`](https://redirect.github.com/percona/percona-xtradb-cluster-operator/releases/tag/v1.19.0)\n\n[Compare
        Source](https://redirect.github.com/percona/percona-xtradb-cluster-operator/compare/v1.18.0...v1.19.0)\n\n#####
        Release Highlights\n\nThis release of Percona Operator for MySQL based on
        Percona XtraDB Cluster includes the following new features and improvements:\n\n#####
        Ensure data security for Percona XtraDB Cluster 8.4 with data-at-rest encryption\n\nData
        at rest encryption ensures that sensitive information stored on disk remains
        protected from unauthorized access, even if the physical media is compromised.
        It is a foundational safeguard for compliance, trust and security in modern
        database environments.\n\nThe Operator supports data at rest encryption for
        MySQL 8.0 with HashiCorp Vault using the `keyring_vault` *plugin*. Now, it
        also supports data at rest encryption for MySQL 8.4, leveraging the `keyring_vault`
        *component*.\n\nThis enhancement enables you to benefit from the rich feature
        set of the latest major version of Percona XtraDB Cluster 8.4 while ensuring
        your sensitive data is secured. In doing so, you can meet compliance requirements
        and protect critical information without added operational complexity. Learn
        how to [configure data at rest encryption for Percona XtraDB Cluster 8.4](https://docs.percona.com/percona-operator-for-mysql/pxc/encryption-setup.html).\n\n#####
        Percona XtraDB Cluster 8.4 is now fully supported\n\nPercona XtraDB Cluster
        8.4 is now fully supported and recommended for production deployments. Starting
        with this release, it becomes the default version for all new database cluster
        deployments using the Operator. This support enables you to benefit from its
        latest features, performance improvements, and enhanced security.\n\n#####
        Use your own CA certificates for TLS verification\n\nYou can now use your
        organization\u2019s custom Certificate Authority (CA) to securely verify TLS
        communication with S3 storage during backups and restores.\n\nThe configuration
        is straightforward: create the Secret that stores your custom CA and certificates
        to authorize in the S3 storage. Then reference this Secret and specify the
        CA certificate in the `caBundle` option in the Operator Custom Resource. The
        Operator will verify TLS communication against it.\n\nHere's the example configuration:\n\n```yml\nstorages:\n
        \ minio-s3:\n    type: s3\n    verifyTLS: true\n    s3:\n      caBundle:\n
        \        name: minio-ca-bundle\n         key: tls.crt\n```\n\nWith this improvement,
        you ensure the following:\n\n- Security without compromise \u2013 no more
        bypassing identity checks.\n- Alignment with your internal standards \u2013
        use the CA your company already trusts.\n- Confidence in backup and restore
        flows \u2013 every S3 interaction is properly verified.\n\nRead more about
        the use of own CA certificates in our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/backups-storage.html#configure-tls-verification-with-custom-certificates-for-s3-storage)\n\n#####
        Configure duration for certificates issued by cert-manager\n\nBy default,
        the `cert-manager` generates certificates valid for 90 days. You now have
        more control over certificate lifetimes and can configure their custom duration
        when you create a new cluster. This way you can align with your organization's
        security and compliance policies.\n\nUse the following Custom Resource options
        to configure certificate duration:\n\n- `.spec.tls.certValidityDuration` \u2013
        validity period for generated certificates\n- `.spec.tls.caValidityDuration`
        \u2013 validity period for the Certificate Authority (CA)\n\n```yaml\n  tls:\n
        \   enabled: true\n    certValidityDuration: 2160h\n    caValidityDuration:
        26280h\n```\n\nNote that the Operator enforces minimum durations to certificates:\n\n-
        For TLS certificates \u2013 1 hour\n- For CA certificate \u2013 730 hours.\n\nAlso,
        we don't recommend setting duration to exactly 1 hour to prevent certificate
        generation issues. Read more about rules and limitations about certificate
        duration configuration in our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/tls-cert-manager.html#customize-certificate-duration-for-cert-manager).\n\nThis
        improvement empowers you to fine-tune certificate lifetimes while keeping
        your cluster secure and stable.\n\n##### Security context for ProxySQL sidecar
        containers\n\nYou can now define the security context for ProxySQL sidecar
        containers in the Operator, reducing the risk of unsecured sidecars bypassing
        Pod restrictions. This improvement lets you set user IDs, privileges, and
        filesystem access directly, ensuring compliance and strengthening Pod security.\n\nConfigure
        the security context in your custom resource. For example:\n\n```yaml\nspec:\n
        \ proxysql:\n       sidecars:\n          securityContext:\n              privileged:
        false\n```\n\nWith this change, you enforce safer defaults across your deployments
        and close security gaps at the Pod level.\n\n##### Improved load balancing
        with ProxySQL scheduler (tech preview)\n\nThe Operator now integrates with
        the external `pxc_scheduler_handler` tool to improve query routing. This feature
        is currently in tech preview, so we recommend experimenting with it in test
        or staging environments before using it in production.\n\nWith this scheduler
        you get finer control over how your SQL queries are routed within your PXC
        cluster:\n\n- SELECT queries (that don't use FOR UPDATE) are intelligently
        distributed across all PXC nodes\u2014or all nodes except the writer, depending
        on your settings.\n- Non-SELECT queries and SELECT FOR UPDATE statements are
        routed to the writer node.\n- You don't have to micromanage the writer role:
        the scheduler automatically ensures only one writer is active at any time.\n\nThis
        means you could see:\n\n- better performance and higher throughput from distributing
        query loads\n- greater reliability with no single point of failure\n\n* Improved
        cluster health through early detection of replication lag and node issues\n\n-
        more efficient use of your resources and hardware\n- a smoother, more predictable
        experience for everyone using the database\n\nSee our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/proxysql-conf.html#proxysql-scheduler-tech-preview)
        for full information about the scheduler behavior and setup.\n\nThe previous
        internal scheduler remains enabled by default to maintain backward compatibility.
        You can switch to the new one when you're ready to benefit from smarter query
        handling.\n\n##### Customize HAProxy backend health check intervals and failover
        behavior\n\nYou can now control how quickly HAProxy detects and reacts to
        node failures. Instead of waiting the default 20 seconds while HAProxy performs
        the failover, you can tune health checks to cut that down to just a few seconds.
        That means your applications recover faster, and users don't get stuck with
        hanging sessions when a node goes down.\n\nYou no longer need to override
        the entire HAProxy configuration to achieve this \u2014 the operator now gives
        you simple, direct options in the Custom Resource specification:\n\n```yaml\nhaproxy:
        \ \n   healthCheck:\n       interval: 10000\n       rise: 1\n       fall:
        2\n```\n\nBy adjusting how often checks run and how many failures or successes
        mark a node as \u201Cdown\u201D or \u201Cup,\u201D you get faster failover,
        cleaner client handling, and easier configuration that is safe to upgrade
        and tailored to your environment.\n\n##### Switch from HAProxy to ProxySQL
        at runtime\n\nYou can now switch from HAProxy to ProxySQL without redeploying
        your Percona XtraDB Cluster. Previously, you had to choose ProxySQL only at
        startup. Now ProxySQL has the `caching_sha2_password` as the default authentication
        plugin, which gives you the flexibility to start with HAProxy and migrate
        to ProxySQL later as your needs evolve.\n\nWith this release, ProxySQL also
        includes a new [scheduler](#improved-load-balancing-with-proxysql-scheduler-tech-preview)
        that enhances SQL awareness, automates read/write splitting, and handles failovers
        more intelligently. This leads to faster queries, increased reliability, and
        more efficient cluster resource usage.\n\n**Which proxy should you choose?**\n\n-
        **HAProxy:** Choose HAProxy if you need a lightweight, TCP-level load balancer
        with minimal configuration. Note that for read/write splitting, your clients
        must connect to different HAProxy ports based on the query type.\n- **ProxySQL:**
        Opt for ProxySQL if you want built-in read/write splitting, advanced query-level
        control, and automated failover logic right out of the box.\n\nEach proxy
        brings its own resource requirements and advantages. We offer [additional
        guidance](https://docs.percona.com/percona-operator-for-mysql/pxc/load-balancing.html#what-load-balancer-to-use)
        on selecting the right proxy for your environment, plus [detailed recommendations](https://docs.percona.com/percona-operator-for-mysql/pxc/proxy-switching.html)
        on resource planning and best practices. Review these carefully to ensure
        your choice fits your operational and performance needs.\n\nTo switch between
        proxies, update your Custom Resource to set `haproxy.enabled` to `false` and
        `proxysql.enabled` to `true`. Apply the changes, and the Operator will handle
        the transition for you by restarting the relevant proxy Pods.\n\nWith this
        improvement you now control your proxy choice at runtime, and ProxySQL brings
        smarter routing and resilience right into the Operator.\n\n##### ProxySQL
        3 support\n\nYou can now deploy ProxySQL 3 with Percona Operator for MySQL.
        This gives you more flexibility and control over how your applications connect
        to MySQL inside Kubernetes. Here\u2019s what you get:\n\n- Dual\u2011password
        support enables you to introduce a new password while the old one is still
        valid. As a result, you can rotate passwords without downtime\n- Enhanced
        event and query logging gives you real\u2011time visibility into query behavior
        and application traffic.\n- ProxySQL now logs the actual values bound to prepared
        statements. This helps you debug queries more effectively, since you see what
        data was passed instead of just placeholders\n- Event logs now include metadata
        about ProxySQL version and format. This makes it easier to track and audit
        logs across upgrades in your Operator\u2011managed deployments.\n\n##### Direct-access
        backups: Improved performance and reliability with sidecars (tech preview)\n\nBy
        default, the Operator makes backups using the SST method. This creates a separate
        backup Pod with Percona XtraBackup, while the database node enters Donor state
        and stops serving client requests. SST backups can also fail with cryptic
        network errors, making root cause analysis and recovery difficult.\n\nStarting
        with version 1.19.0, you can make backups via the XtraBackup sidecar container.
        The Operator deploys a sidecar with XtraBackup inside each Percona XtraDB
        Cluster Pod. This sidecar makes a backup and uploads it to the remote backup
        storage. The database Pod doesn\u2019t change its state to Donor and keeps
        accepting client requests.\n\nUsing the sidecar method provides a direct access
        to data thus boosting backup performance. The sidecar container constantly
        runs in the database Pod, so you have constant access to logs and status,
        which simplifies troubleshooting.\n\nTo enable the XtraBackup sidecar container
        backup method, set `PXCO_FEATURE_GATES=XtrabackupSidecar=true` environment
        variable in the Operator Deployment.\nThis functionality is in the tech preview
        stage and currently supports only cloud storages. We encourage you to try
        it out in your testing or staging environments and leave your feedback.\n\nFuture
        enhancements such as support of PVC volumes, backup encryption and incremental
        backups are planned for future releases.\n\nTo learn more about XtraBackup
        sidecar container backup method, see our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/backups.html#xtrabackup-sidecar-method-tech-preview).\n\n#####
        Ensure only up to date data is served during backups\n\nWhen a node donates
        data during backups or SST, it enters into the DONOR state. At this point,
        the node should no longer handle client connections. HAProxy's external check
        correctly blocked new connections to the Donor node but allowed existing sessions
        to remain active. Those lingering sessions could return slow or outdated results.\n\nThe
        HAProxy default configuration now includes the `on-marked-down shutdown-sessions`
        directive. As soon as HAProxy marks a node as down, all active connections
        are immediately closed and clients reconnect to remaining active nodes. This
        ensures that only fresh, up to date data is served during backups.\n\n#####
        Automatic cleanup of backup and restore Jobs and associated Pods\n\nThe Operator
        creates a dedicated Job and Pod for every backup and restore operation. Previously,
        these Jobs and Pods remained in the cluster even after the operation was finished,
        and you had to manually delete them to free up resources.\n\nNow, you can
        offload this task to the Operator. Specify a time-to-live (TTL) for backup
        and restore Jobs once the operation is finished. When the TTL expires, the
        Operator automatically deletes the Job and its associated Pod.\n\nModify your
        Custom Resource as follows:\n\n```yaml\nbackup:\n  image: perconalab/percona-xtradb-cluster-operator:main-pxc8.0-backup\n
        \ ttlSecondsAfterFinished: 3600\n```\n\nThis setting is global. It applies
        to all on-demand and scheduled backups, and all restores.\n\nThe Operator
        also ensures reliability: if a backup or restore takes longer than the configured
        TTL, it applies the `internal.percona.com/keep-job` finalizer to allow the
        operation to finish. After the operation completes either with the `Succeeded`
        or the `Failed` status, the finalizer is removed and the Job is cleaned up.\n\nThis
        improvement reduces manual maintenance overhead, gives you control over the
        processes lifetime for debugging or auditing purposes and helps keep your
        cluster healthy and efficient. By reducing unnecessary resource buildup, you
        gain smoother operations, lower maintenance overhead and improved reliability
        in production environments.\n\n##### Improved backup identification for point-in-time
        recovery readiness\n\nWhen a backup contains binlog gaps, the Operator now
        creates a `<backup-name>.pitr-not-ready` file in the backup storage. This
        file makes it easy to identify which backups are appropriate for point in
        time recovery both in the storage and when listing backup objects.\n\nBefore
        starting a restore, the Operator checks for this marker file and blocks unsafe
        restores, protecting you from incomplete recovery attempts. If needed, you
        can override this safeguard by adding the `percona.com/unsafe-pitr` annotation
        to the Restore object. Use this override with caution, as this is an unsafe
        configuration.\n\n##### Attach external PVCs for shared data access across
        applications and the database cluster\n\nSometimes your database needs more
        than its own internal storage. For example, it needs access to reference files,
        shared configuration files or lookup tables generated outside the database
        but still essential for queries and procedures.\n\nYou can now attach auxiliary
        pre-existing PVCs and mount that external data directly into your database,
        ProxySQL or HAProxy pods in a clean, declarative way using the Custom Resource.\n\nThis
        example configuration shows how to attach external PVC to the XtraDB Cluster
        Pods:\n\n```yaml\npxc:\n  extraPVCs:\n    - name: extra-data-volume\n      claimName:
        my-extra-storage\n      mountPath: /var/lib/mysql-extra\n      readOnly: false\n```\n\nThis
        improvement gives you a reliable way to separate internal database storage
        from external domain data, update shared datasets independently, and still
        benefit from the Operator\u2019s automation and resilience.\n\n##### Customize
        password generation by the Operator\n\nBy default, the Operator generates
        user passwords using alphanumeric characters plus a set of special symbols.
        Some tools such as MySQL Prometheus Exporter or mysqlsh don't support certain
        symbols, which can make those passwords invalid.\n\nTo improve compatibility
        and user experience, you can now customize password generation parameters
        in the Custom Resource:\n\n```yaml\nspec:\n passwordGenerationOptions:\n   symbols:
        \"!#$%&()*+,-.<=>?@&#8203;[]^_{}~\"\n   maxLength: 20\n   minLength: 16\n```\n\nThis
        enhancement lets you keep the convenience of automated password generation
        and at the same time ensure compliance with the tools and environments you
        integrate with the Operator.\n\n##### Configure memory allocator in the Operator\n\nBy
        default, Percona Operator for XtraDB Cluster uses the system allocator (`libc`)
        to manage memory. While this works for most cases, alternative allocators
        such as `jemalloc` and `tcmalloc` can improve performance and reduce fragmentation
        in high-traffic workloads.\n\nTo have more flexibility, you can now configure
        the memory allocator directly in the Custom Resource:\n\n```yaml\nspec:\n
        \  pxc:\n     mysqlAllocator: jemalloc\n```\n\nSupported values are:\n\n-
        `jemalloc`\n- `tcmalloc`\n- `libc` (default, used when no value is set)\n\nIf
        you have already configured the memory allocator via the environment variable,
        the Operator will respect that setting and use it instead of the Custom Resource
        value.\n\nThis enhancement lets you fine-tune memory management for your cluster
        while keeping compatibility with existing configurations.\n\n##### Deprecation,
        rename, removal\n\n**Removed in 1.19.0:**\n\n- `proxysql.readinessDelaySec`
        and `proxysql.livenessDelaySec` fields are removed as redundant\n\n**Deprecated
        (will be removed in 1.22.0):**\n\n- `pxc.livenessDelaySec`. Use [`pxc.livenessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pxclivenessprobesinitialdelayseconds)\n-
        `pxc.readinessDelaySec`. Use [`pxc.readinessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pxcreadinessprobesinitialdelayseconds)\n-
        `haproxy.livenessDelaySec`. Use [`haproxy.livenessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#haproxylivenessprobesinitialdelayseconds)\n-
        `haproxy.readinessDelaySec`. Use [`haproxy.readinessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#haproxyreadinessprobesinitialdelayseconds)\n\n#####
        Changelog\n\n##### New Features\n\n- [K8SPXC-1332](https://perconadev.atlassian.net/browse/K8SPXC-1332)
        - Added the ability to load custom SSL certificates for backup operations
        to S3 storage. This enables secure communication with S3-compatible storage
        using the certificates approved and trusted by your company (Thank you Azam
        Abdoelbasier for submitting this request).\n- [K8SPXC-1494](https://perconadev.atlassian.net/browse/K8SPXC-1494)
        - Added the ability to configure the duration of TLS certificates created
        by `cert-manager`. This allows users to customize certificate lifecycles to
        meet their specific security requirements.\n- [K8SPXC-1576](https://perconadev.atlassian.net/browse/K8SPXC-1576)
        - Added the ability to use the XtraBackup sidecar container instead of SST
        for creating backups. This provides an alternative, potentially more efficient
        backup method.\n- [K8SPXC-1688](https://perconadev.atlassian.net/browse/K8SPXC-1688)
        - Added ability to mount pre-existing auxiliary PVCs as volumes to database
        and proxy pods. This facilitates easier integration with external data and
        storage resources (Thank you Emin AKTAS for submitting the request and contributing
        to it).\n- [K8SPXC-1733](https://perconadev.atlassian.net/browse/K8SPXC-1733)
        - Added the ability to customize password generation parameters, such as length
        and character sets via the Custom Resource. This ensures smooth operation
        of the tools with specific requirements towards password and leverages the
        automatic password generation of the Operator (Thank you user fydrah for submitting
        the request and contributing to it).\n- [K8SPXC-1734](https://perconadev.atlassian.net/browse/K8SPXC-1734)
        - Introduced configurable HAProxy backend health check parameters that can
        be tuned without overriding the entire configuration. This simplifies performance
        tuning for high-availability setups (Thank you Tim Stoop for submitting the
        request and contributing to it).\n\n##### Improvements\n\n- [K8SPXC-735](https://perconadev.atlassian.net/browse/K8SPXC-735)
        - Added the support of the `pxc_scheduler_handler` ProxySQL scheduler for
        SQL-aware routing and effective read/write splitting. This allows for better
        utilization of resources by distributing read-only traffic across the entire
        cluster while routing write requests only to the writer node.\n- [K8SPXC-992](https://perconadev.atlassian.net/browse/K8SPXC-992)
        - Improved binlog naming to prevent potential collisions between different
        collectors. The updated naming convention ensures unique and consistent identification
        of binary log files in storage.\n- [K8SPXC-1144](https://perconadev.atlassian.net/browse/K8SPXC-1144)
        - Introduced a mechanism to mark S3 backups as PITR-unready if binlog gaps
        are detected. This prevents users from attempting invalid point-in-time recoveries
        using inconsistent backups.\n- [K8SPXC-1214](https://perconadev.atlassian.net/browse/K8SPXC-1214)
        - Added an option to automatically clean up completed backup and restore jobs
        and their associated pods. This improvement helps reduce pressure on the Kubernetes
        API by removing stale resources (Thank you Alexandre Barth for reporting this
        issue).\n- [K8SPXC-1319](https://perconadev.atlassian.net/browse/K8SPXC-1319)
        - Enhanced the operator to support running multiple backup restores for different
        clusters in parallel. This removes a previous limitation that blocked concurrent
        restore operations across the environment.\n- [K8SPXC-1327](https://perconadev.atlassian.net/browse/K8SPXC-1327)
        - Added the ability to change the memory allocator for MySQL to improve memory
        management efficiency. This change helps optimize the overall memory footprint
        of PXC pods.\n- [K8SPXC-1373](https://perconadev.atlassian.net/browse/K8SPXC-1373)
        - Improved core dump handling to ensure that crashed instances can recover
        more reliably after an SST. This enhancement aids in diagnosing and recovering
        from unexpected server failures.\n- [K8SPXC-1431](https://perconadev.atlassian.net/browse/K8SPXC-1431)
        - Improved the delete-backup finalizer logic to correctly handle the deletion
        of on-demand backup PVCs.\n- [K8SPXC-1470](https://perconadev.atlassian.net/browse/K8SPXC-1470)
        - Added the ability to switch between HAProxy and ProxySQL within an existing
        cluster. This provides users with more flexibility to change their load-balancing
        solution as their needs evolve.\n- [K8SPXC-1511](https://perconadev.atlassian.net/browse/K8SPXC-1511)
        - Added the support of data at rest encryption for Percona XtraDB Cluster
        8.4 via the `keyring vault` component. This change ensures compatibility with
        the latest security architecture of MySQL 8.4.\n- [K8SPXC-1525](https://perconadev.atlassian.net/browse/K8SPXC-1525)
        - Deprecated `pxc.livenessDelaySec` option in favor of more consistent liveness
        probe parameters. The Operator now prioritizes standard probe configurations
        to manage Pod lifecycle.\n- [K8SPXC-1568](https://perconadev.atlassian.net/browse/K8SPXC-1568)
        - Updated the Operator's password generation logic to prevent the '\\*' character
        from being used as the first character. This avoids potential issues with
        certain authentication plugins and command-line tools.\n- [K8SPXC-1594](https://perconadev.atlassian.net/browse/K8SPXC-1594)
        - Improved the database upgrade logic to prevent the controller from being
        blocked during the operation. This ensures that the Operator remains responsive
        to other cluster changes while an upgrade is in progress.\n- [K8SPXC-1628](https://perconadev.atlassian.net/browse/K8SPXC-1628)
        - Added support for `tcmalloc` as an alternative memory allocator in PXC images.
        This gives users additional options to tune and reduce the memory footprint
        of their database workloads.\n- [K8SPXC-1647](https://perconadev.atlassian.net/browse/K8SPXC-1647)
        - Implemented extended exit codes for garbd to provide better diagnostic information
        for different failure scenarios. This helps users identify the root cause
        of SST and joining issues faster.\n- [K8SPXC-1668](https://perconadev.atlassian.net/browse/K8SPXC-1668)
        - Added support for ProxySQL 3, providing users with access to the latest
        features and performance improvements of the load balancer.\n- [K8SPXC-1683](https://perconadev.atlassian.net/browse/K8SPXC-1683)
        - Expanded smart update tests to include PXC 8.4 and PMM 3, ensuring stable
        upgrade paths for the latest versions.\n- [K8SPXC-1703](https://perconadev.atlassian.net/browse/K8SPXC-1703)
        - Added the support of the `generateEmbeddedObjectMeta` option, improving
        the template handling for sidecars and extra PVCs (Thank you Emin AKTAS for
        reporting and contributing to this issue).\n- [K8SPXC-1748](https://perconadev.atlassian.net/browse/K8SPXC-1748)
        - Eliminated runtime CREATE FUNCTION statements in the PITR collector to avoid
        unnecessary Galera TOI (Total Order Isolation) events. This reduces the performance
        impact on the cluster when the PITR sidecar starts or restarts.\n\n##### Bugs
        Fixed\n\n- [K8SPXC-926](https://perconadev.atlassian.net/browse/K8SPXC-926)
        - Fixed an issue where a failed smart update on one cluster could block the
        Operator from managing other clusters in multi-cluster environments. The controller
        now handles update failures more gracefully without impacting independent
        resources.\n- [K8SPXC-1379](https://perconadev.atlassian.net/browse/K8SPXC-1379)
        - Fixed an issue where monit container resource values in ProxySQL pods did
        not correctly reflect the values specified in the PXC cluster definition.
        The operator now ensures that ProxySQL resource attributes are properly applied
        to the monitoring sidecar containers.\n- [K8SPXC-1424](https://perconadev.atlassian.net/browse/K8SPXC-1424)
        - Resolved a certificate renewal issue where CA certificates in TLS secrets
        could expire before server certificates were renewed. The Operator logic was
        updated to align renewal intervals for CA and server certificates when using
        cert-manager.\n- [K8SPXC-1581](https://perconadev.atlassian.net/browse/K8SPXC-1581)
        - Corrected the order of options in the restore prepare job to ensure that
        `--defaults-file` is passed as the first option to xtrabackup. This fix ensures
        that custom configuration files are correctly prioritized during the restore
        process.\n- [K8SPXC-1617](https://perconadev.atlassian.net/browse/K8SPXC-1617)
        - Fixed a binlog gap issue in Point-in-Time Recovery (PITR) that caused repeated
        test failures. Users are now advised to perform a full backup after each PITR
        restore to ensure data consistency and prevent gaps.\n- [K8SPXC-1632](https://perconadev.atlassian.net/browse/K8SPXC-1632)
        - Added missing SecurityContext configurations for ProxySQL sidecar containers
        to enhance pod security. This change ensures that all sidecars follow the
        defined security standards of the cluster.\n- [K8SPXC-1655](https://perconadev.atlassian.net/browse/K8SPXC-1655)
        - Fixed a failure in xtrabackup when using LZ4 compression on RHEL9-based
        Percona XtraDB Cluster images. The fix addresses compatibility issues with
        the latest compression libraries in the operating system environment.\n- [K8SPXC-1686](https://perconadev.atlassian.net/browse/K8SPXC-1686)
        - Improved backup error handling to ensure that providing an invalid Percona
        XtraBackup image results in a failed status. A new timeout field was introduced
        to prevent backup objects from hanging indefinitely in a starting state.\n-
        [K8SPXC-1687](https://perconadev.atlassian.net/browse/K8SPXC-1687) - Fixed
        the `copy-backup.sh` script to correctly handle and copy cloud-based backups
        stored in S3 or Azure. This ensures that the utility script works consistently
        across all supported storage types.\n- [K8SPXC-1701](https://perconadev.atlassian.net/browse/K8SPXC-1701)
        - Ensured that MySQL configurations are correctly mounted to the restore prepare
        job. This fix allows the restore process to use custom MySQL settings defined
        in the cluster (Thank you Emin AKTAS for reporting and contributing to this
        issue).\n- [K8SPXC-1702](https://perconadev.atlassian.net/browse/K8SPXC-1702)
        - Added the ability to override time zones for backup jobs. This resolves
        issues where time-dependent operations could fail due to missing timezone
        definitions (Thank you Emin AKTAS for reporting and contributing to this issue).\n-
        [K8SPXC-1721](https://perconadev.atlassian.net/browse/K8SPXC-1721) - Added
        a sleep interval to the recovery loop to prevent high CPU usage spikes when
        containers restart.\n- [K8SPXC-1725](https://perconadev.atlassian.net/browse/K8SPXC-1725)
        - Fixed a condition where a cluster could return stalled data during a backup
        or SST operation by adding the on-marked-down shutdown-sessions directive
        to HAProxy default configuration. This ensures that only fresh, up to date
        data is served during backups.\n- [K8SPXC-1726](https://perconadev.atlassian.net/browse/K8SPXC-1726)
        - Resolved a deployment breakage in the Operator version 1.18.0 via Helm caused
        by PMM 3 client incompatibilities. The fix ensures a smoother upgrade path
        for users migrating to newer versions of PMM (Thank you Antonio Falzarano
        for reporting and contributing to this issue).\n- [K8SPXC-1760](https://perconadev.atlassian.net/browse/K8SPXC-1760)
        - Fixed the handling of the crVersion field in the Helm chart templates. The
        Operator now correctly considers the version defined in `values.yaml` when
        generating the cluster configuration.\n- [K8SPXC-1771](https://perconadev.atlassian.net/browse/K8SPXC-1771)
        - Fixed the issue with excessive logging by the backup controller when backups
        are suspended or resumed due to an unready cluster. This improves log readability
        and reduces unnecessary diagnostic noise.\n- [K8SPXC-1772](https://perconadev.atlassian.net/browse/K8SPXC-1772)
        - Fixed a state transition bug where unsuspended backups could move directly
        from 'Starting' to 'Succeeded' without entering the 'Running' state. This
        ensures accurate tracking and visibility of the backup process status.\n\n#####
        Documentation Improvements\n\n- [K8SPXC-1747](https://perconadev.atlassian.net/browse/K8SPXC-1747)
        - Improved the documentation with the information about available environment
        variables for cluster components and the Operator. Documented the `S3_WORKERS_LIMIT`
        environment variable to allow throttling of backup deletions.\n- [K8SPXC-1661](https://perconadev.atlassian.net/browse/K8SPXC-1661)
        - Updated the operator documentation to reflect that PMM 3 uses service accounts
        instead of API keys. This ensures that users can correctly configure monitoring
        integration with the latest versions of PMM.\n- [K8SPXC-1663](https://perconadev.atlassian.net/browse/K8SPXC-1663)
        - Improved documentation for Point-in-Time Recovery steps. The updated documentation
        properly separates and sequences the recovery instructions for improved readability.\n\n#####
        Supported Software\n\nThe Operator was developed and tested with the following
        software:\n\n- Percona XtraDB Cluster versions 8.4.7-7.1, 8.0.44-35.1, and
        5.7.44-31.65\n- Percona XtraBackup versions 8.4.0-5.1, 8.0.35-34.1, and 2.4.29\n-
        HAProxy 2.8.17\n- ProxySQL 2.7.3-1.2, 3.0.1-1.2\n- LogCollector based on fluent-bit
        4.0.1-1\n- PMM Client 2.44.1-1 and 3.5.0\n\nOther options may also work but
        have not been tested.\n\n##### Supported Platforms\n\nPercona Operators are
        designed for compatibility with all [CNCF-certified](https://www.cncf.io/training/certification/software-conformance/)
        Kubernetes distributions. Our release process includes targeted testing and
        validation on major cloud provider platforms and OpenShift, as detailed below:\n\n-
        [Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine)
        1.31 - 1.33\n- [Amazon Elastic Container Service for Kubernetes (EKS)](https://aws.amazon.com)
        1.32 - 1.34\n- [Azure Kubernetes Service (AKS)](https://azure.microsoft.com/en-us/services/kubernetes-service/)
        1.32 - 1.34\n- [OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift)
        4.17 - 4.20\n- [Minikube](https://minikube.sigs.k8s.io/docs/) 1.37.0 based
        on Kubernetes 1.34.0\n\nThis 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.\n\n### [`v1.18.0`](https://redirect.github.com/percona/percona-xtradb-cluster-operator/releases/tag/v1.18.0)\n\n[Compare
        Source](https://redirect.github.com/percona/percona-xtradb-cluster-operator/compare/v1.17.0...v1.18.0)\n\n#####
        Release Highlights\n\nThis release of Percona Operator for MySQL based on
        Percona XtraDB Cluster includes the following new features and improvements:\n\n#####
        PMM3 support\n\nThe Operator is natively integrated with [PMM 3](https://www.percona.com/doc/percona-monitoring-and-management/3/index.html),
        enabling you to monitor the health and performance of your Percona Distribution
        for MySQL deployment and at the same time enjoy enhanced performance, new
        features, and improved security that PMM 3 provides.\n\nNote that the Operator
        supports both PMM2 and PMM3. The decision on what PMM version is used depends
        on the authentication method you provide in the Operator configuration: PMM2
        uses API keys while PMM3 uses service account token. If the Operator configuration
        contains both authentication methods with non-empty values, PMM3 takes the
        priority.\n\nTo use PMM, ensure that the PMM client image is compatible with
        the PMM Server version. Check [Percona certified images](https://docs.percona.com/percona-operator-for-mysql/pxc/images.html)
        for the correct client image.\n\nFor how to configure monitoring with PMM,
        see the [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/monitoring.html).\n\n#####
        Improved monitoring for clusters in multi-region or multi-namespace deployments
        in PMM\n\nNow you can define a custom name for your clusters deployed in different
        data centers. This name helps Percona Management and Monitoring (PMM) Server
        to correctly recognize clusters as connected and monitor them as one deployment.
        Similarly, PMM Server identifies clusters deployed with the same names in
        different namespaces as separate ones and correctly displays performance metrics
        for you on dashboards.\n\nTo assign a custom name, define this configuration
        in the Custom Resource manifest for your cluster:\n\n```yaml\nspec:\n  pmm:\n
        \   customClusterName: testClusterName\n```\n\n##### More resilient database
        restores without matching user Secrets\n\nYou no longer need matching user
        Secrets between your backup and your target cluster to perform a restore.
        The Operator now has a post-restore step that changes user passwords in the
        restored database to the ones from the local Secret. Also, it creates missing
        system users and adds missing grants.\n\nThis flow is the same regardless
        of whether you restore to the same cluster or to a completely new one.\n\nThe
        removal of this major roadblock to have a Secret for restores makes your disaster
        recovery process smoother and more reliable. This enhancement makes managing
        databases on Kubernetes more robust and operator-friendly.\n\n##### Improved
        backup retention for streamlined management of scheduled backups in cloud
        storage\n\nA new backup retention configuration gives you more control over
        how backups are managed in storage and retained in Kubernetes.\n\nWith the
        `deleteFromStorage` flag , you can disable automatic deletion from AWS S3
        or Azure Blob storage and instead rely on native cloud lifecycle policies.
        This makes backup cleanup more efficient and better aligned with flexible
        storage strategies.\n\nThe legacy `keep` option is now deprecated and mapped
        to the new `retention` block for compatibility. We encourage you to start
        using the `backup.schedule.retention` configuration:\n\n```yaml\nschedule:\n
        \ - name: \"sat-night-backup\"\n    schedule: \"0 0 * * 6\"\n    retention:\n
        \     count: 3\n      type: count\n      deleteFromStorage: true\n    storageName:
        s3-us-west\n```\n\nNote that if you have both `backup.schedule.keep`  and
        `backup.schedule.retention`  defined, the `backup.schedule.retention` takes
        precedence.\n\n##### Added labels to identify the version of the Operator\n\nCustom
        Resource Definition (CRD) is compatible with the last three Operator versions.
        To know which Operator version is attached to it, we've added labels to all
        Custom Resource Definitions. The labels help you identify the current Operator
        version and decide if you need to update the CRD. To view the labels, run:
        `kubectl get crd perconaxtradbclusters.pxc.percona.com --show-labels`.\n\n#####
        Cross-site replication is now supported for Percona XtraDB Cluster 8.4\n\nCross-site
        replication is now available with Percona XtraDB Cluster 8.4.x, lifting one
        of the  limitations in the Operator for this database version. This enhancement
        marks a significant step toward general availability of Percona XtraDB Cluster
        8.4 in the Operator by enabling multi-site deployments and improving resilience
        across distributed environments.\n\n##### Deprecation, Rename and Removal\n\n-
        The `pxc.expose.loadBalancerIP`, `haproxy.exposePrimary.loadBalancerIP`, `haproxy.exposeReplicas.loadBalancerIP`
        and `proxysql.expose.loadBalancerIP` keys are deprecated. The `loadBalancerIP`
        field is also deprecated upstream in Kubernetes\n  due to its inconsistent
        behavior across cloud providers and lack of dual-stack support. As a result,
        its usage is strongly discouraged.\n\n  We recommend using cloud provider-specific
        annotations instead, as they offer more predictable and portable behavior
        for managing load balancer IP assignments.\n\n  The `pxc.expose.loadBalancerIP`,
        `haproxy.exposePrimary.loadBalancerIP`, `haproxy.exposeReplicas.loadBalancerIP`
        and `proxysql.expose.loadBalancerIP` keys are scheduled for removal in future
        releases.\n\n- The `backup.schedule.keep` field is deprecated and will be
        removed after release 1.21.0. We recommend using the `backup.schedule.retention`
        instead as follows:\n\n  ```yaml\n  schedule:\n    - name: \"sat-night-backup\"\n
        \     schedule: \"0 0 ** 6\"\n      retention:\n        count: 3\n        type:
        count\n        deleteFromStorage: true\n      storageName: s3-us-west\n  ```\n\n-
        New repositories for Percona XtraBackup and Logcollector\n\n  Now the Operator
        uses the official Percona Docker images for the `percona-xtrabackup` and `logcollector`
        components. Pay attention to the new image repositories when you upgrade the
        Operator and the database. Check the [Percona certified images](https://docs.percona.com/percona-operator-for-mysql/pxc/images.html)
        for exact image names.\n\n- Changes for Helm charts:\n\n  - PMM3 is now the
        default. To keep using PMM2, set the `pmm.tag: 2.44.1`\n  - If you install
        or upgrade the Operator with default manifests using Helm charts on Openshift
        4.19, you must use the `docker.io` registry prefix to guarantee successful
        download from the DockerHub `percona-xtradb-cluster` repository. Read the
        [Considerations for using OpenShift 4.19](#considerations-for-using-openshift-419)
        section for more information.\n\n##### Known limitations\n\n##### Considerations
        for using OpenShift 4.19\n\nStarting with OpenShift 4.19, the way images with
        not fully qualified names are pulled has changed for repositories that share
        the same repository name on DockerHub and Red Hat Marketplace. By default
        the tags are pulled from Red Hat Marketplace. Specifying not fully qualified
        image names may result in the `ImagePullBackOff` error.\n\n- **OLM installation:**
        Images are provided with the fully qualified names and are pulled from the
        Red Hat Marketplace/DockerHub registry.\n- **Manual install/update with default
        manifests:** Images must use the `docker.io` registry prefix to guarantee
        successful download from the Dockerhub `percona-xtradb-cluster` repository.\n\nSee
        our documentation for [manual installation](https://docs.percona.com/percona-operator-for-mysql/pxc/openshift.html#install-the-operator-via-the-command-line-interface)
        or [update](https://docs.percona.com/percona-operator-for-mysql/pxc/update_openshift.html#update-via-the-command-line-interface).\n\n#####
        Changleog\n\n##### New Features\n\n- [K8SPXC-1284](https://perconadev.atlassian.net/browse/K8SPXC-1284)
        - Add the ability to configure protocol for peer-list DNS SRV lookups\n\n-
        [K8SPXC-1599](https://perconadev.atlassian.net/browse/K8SPXC-1599) - Allowed
        setting `loadBalancerClass` service type and using a custom implementation
        of a load balancer rather than the cloud provider default one\n\n##### Improvements\n\n-
        [K8SPXC-1375](https://perconadev.atlassian.net/browse/K8SPXC-1375) - Added
        a new retention configuration to allow users to delegate backup cleanup to
        cloud lifecycle policies (Thank you user Tristan for reporting this issue)\n\n-
        [K8SPXC-1376](https://perconadev.atlassian.net/browse/K8SPXC-1376) - Added
        the ability to restore from backup without a matching Secret resource\n\n-
        [K8SPXC-1399](https://perconadev.atlassian.net/browse/K8SPXC-1399) - Added
        a documentation how to set up a disaster recovery system and transfer workloads
        between sites\n\n- [K8SPXC-1415](https://perconadev.atlassian.net/browse/K8SPXC-1415)
        - Updated the `percona-xtrabackup` image to use the official `percona-xtrabackup`
        Docker image\n\n- [K8SPXC-1430](https://perconadev.atlassian.net/browse/K8SPXC-1430)
        - Improved handling of autogenerated certificates depending on the `delete-ssl`
        finalizer configuration\n\n- [K8SPXC-1448](https://perconadev.atlassian.net/browse/K8SPXC-1448),
        [K8SPXC-1449](https://perconadev.atlassian.net/browse/K8SPXC-1449) - Improved
        the `pvc-resize` test by using a custom storage class for EKS, reducing errors
        and improving the quota handling during resize\n\n- [K8SPXC-1450](https://perconadev.atlassian.net/browse/K8SPXC-1450)
        - Improved PVC resizing behavior when reducing the storage size by reverting
        the values when the quota is reached\n\n- [K8SPXC-1472](https://perconadev.atlassian.net/browse/K8SPXC-1472)
        - Deprecated the `loadBalancerIP` field due to its deprecation upstream\n\n-
        [K8SPXC-1513](https://perconadev.atlassian.net/browse/K8SPXC-1513) - Added
        PXC 8.4 support for version service\n\n- [K8SPXC-1529](https://perconadev.atlassian.net/browse/K8SPXC-1529)
        - Added support for cross-site replication with MySQL 8.4.0 by adding the
        use of `authentication_policy` instead of `default_authentication_plugin`\n\n-
        [K8SPXC-1553](https://perconadev.atlassian.net/browse/K8SPXC-1553) - Added
        support for PMM v3\n\n- [K8SPXC-1560](https://perconadev.atlassian.net/browse/K8SPXC-1560)
        - Added the warning about CRDs not being upgraded automatically after helm
        upgrade to the output\n\n- [K8SPXC-1566](https://perconadev.atlassian.net/browse/K8SPXC-1566)
        - Improved reconciliation of replicationChannels without proxy Pods by starting
        the database Pod bypassing the proxy (Thank you Justin Reasoner for contributing
        to this issue)\n\n- [K8SPXC-1569](https://perconadev.atlassian.net/browse/K8SPXC-1569)
        - Added Labels for Custom Resource Definitions (CRD) to identify the Operator
        version attached to them\n\n- [K8SPXC-1597](https://perconadev.atlassian.net/browse/K8SPXC-1597)
        - Improve the scheduled backups behavior for a cluster in an unhealthy state
        by postponing the job until the cluster reports the healthy status\n\n- [K8SPXC-1605](https://perconadev.atlassian.net/browse/K8SPXC-1605)
        - Introduced Azure CLI for checking if backup objects/folders exist in Azure
        storage\n\n- [K8SPXC-1612](https://perconadev.atlassian.net/browse/K8SPXC-1612)
        - Added the `imagePullSecrets` for PMM image\n\n- [K8SPXC-1615](https://perconadev.atlassian.net/browse/K8SPXC-1615)
        - Added the ability to define a custom cluster name for `pmm-admin` component\n\n-
        [K8SPXC-1624](https://perconadev.atlassian.net/browse/K8SPXC-1624) - Deleted
        deprecated finalizers code\n\n- [K8SPXC-1669](https://perconadev.atlassian.net/browse/K8SPXC-1669)
        - Improve the backup flow by generating a default endpoint URL for a storage
        from a region if it is not provided (Thank you Bernard Grymonpon for reporting
        this issue)\n\n- [K8SPXC-1677](https://perconadev.atlassian.net/browse/K8SPXC-1677)
        - Document the changed behavior with pulling images for default manifests
        on OpenShift 4.19 and update install and update instructions\n\n##### Bugs
        Fixed\n\n- [K8SPXC-1312](https://perconadev.atlassian.net/browse/K8SPXC-1312)
        - Fixed the issue with labels not being updated automatically for point-in-time
        recovery deployment upon Custom Resource changes\n\n- [K8SPXC-1347](https://perconadev.atlassian.net/browse/K8SPXC-1347)
        - Fixed the issue with point-in-time recovery failing due to TLS configuration
        mismatch between the server and the point-in-time recovery job by configuring
        it to use TLS if is required by the server.\n\n- [K8SPXC-1382](https://perconadev.atlassian.net/browse/K8SPXC-1382)
        - Fixed the issue with backup failing on AWS if using IAM profile without
        credentialsSecret by using credentialsSecret only when explicitly specified
        and relying on IAM roles instead (Thank you Itiel Olenick for reporting this
        issue)\n\n- [K8SPXC-1541](https://perconadev.atlassian.net/browse/K8SPXC-1541)
        - Fixed Telemetry module to to consider both empty string \"\" and comma separated
        namespaces in cluster-wide mode\n\n- [K8SPXC-1548](https://perconadev.atlassian.net/browse/K8SPXC-1548)
        Fixed the issue with deleting old backups on Google Cloud Storage by url-decoding
        the object path before deleting it (Thank you Mateusz Gruszkiewicz for reporting
        this issue)\n\n- [K8SPXC-1631](https://perconadev.atlassian.net/browse/K8SPXC-1631)
        - Fixed the issue with the Operator restarting pod-0 after the cluster is
        ready. The issue is caused by ConfigMap and StatefulSet being created too
        close to each other and Kubernetes API can't return the newly created ConfigMap
        before creating the StatefulSet. The issue is fixed by reconciling the StatefulSet
        after the reconciliation of ConfigMap is completed.\n\n- [K8SPXC-1664](https://perconadev.atlassian.net/browse/K8SPXC-1664)
        - Fixed the use of the proper script to check PXC nodes when adding them by
        HAProxy\n\n##### Supported Software\n\nThe Operator was developed and tested
        with the following software:\n\n- Percona XtraDB Cluster versions 8.4.5-5.1
        (Tech preview), 8.0.42-33.1, and 5.7.44-31.65\n- Percona XtraBackup versions
        8.4.0-3, 8.0.35-34.1, and 2.4.29\n- HAProxy 2.8.15-1\n- ProxySQL 2.7.3\n-
        LogCollector based on fluent-bit 4.0.1\n- PMM Client 2.44.1 and 3.3.1\n\nOther
        options may also work but have not been tested.\n\n##### Supported Platforms\n\nPercona
        Operators are designed for compatibility with all [CNCF-certified](https://www.cncf.io/training/certification/software-conformance/)
        Kubernetes distributions. Our release process includes targeted testing and
        validation on major cloud provider platforms and OpenShift, as detailed below
        for Operator version 1.16.0:\n\n- [Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine)
        1.30 - 1.33\n- [Amazon Elastic Container Service for Kubernetes (EKS)](https://aws.amazon.com)
        1.30 - 1.33\n- [Azure Kubernetes Service (AKS)](https://azure.microsoft.com/en-us/services/kubernetes-service/)
        1.30 - 1.33\n- [OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift)
        4.15 - 4.19\n- [Minikube](https://minikube.sigs.k8s.io/docs/) 1.36.0 based
        on Kubernetes 1.33.1\n\nThis 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.\n\n### [`v1.17.0`](https://redirect.github.com/percona/percona-xtradb-cluster-operator/releases/tag/v1.17.0)\n\n[Compare
        Source](https://redirect.github.com/percona/percona-xtradb-cluster-operator/compare/v1.16.1...v1.17.0)\n\n####
        Release Highlights\n\n##### Improved observability for HAProxy and ProxySQL\n\nGet
        insights into the HAProxy and ProxySQL performance by connecting to their
        statistics pages. Use the `cluster-name-haproxy:8084` and `cluster-name-proxysql:6070`
        endpoints to do so. Learn about other available ports in the [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/haproxy-conf.html).\n\n#####
        Improved cluster load management during backups\n\nIf parallel backups overload
        your cluster, you can turn off parallel execution to prevent this. Previously,
        this meant that you could only run one backup at a time - no new backups could
        start until the current one was finished. Now, the Operator queues backups
        and runs them one after another automatically. You can fine-tune the backup
        sequence by setting the start time for all backups or for a specific on-demand
        one using the [`spec.backup.startingDeadlineSeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#backupstartingdeadlineseconds)
        Custom Resource option. This provides greater control over backup operations.\n\nAnother
        improvement is for the case when your database cluster becomes unhealthy,
        for example, when a Pod crashes or restarts. The Operator suspends running
        backups to reduce the cluster's load. Once the cluster recovers and reports
        a Ready status, the Operator resumes the suspended backup. To further offload
        the cluster during an unhealthy state, you can configure how long a backup
        remains suspended by using the [`spec.backup.suspendedDeadlineSeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#backupsuspendeddeadlineseconds)
        Custom Resource option. If this time expires before the cluster recovers,
        the backup is marked as \"failed.\"\n\n##### Monitor PMM Client health and
        status\n\nPercona Monitoring and Management (PMM) is a great tool to [monitor
        the health of your database cluster](https://docs.percona.com/percona-operator-for-mysql/pxc/monitoring.html).
        Now you can also learn if PMM itself is healthy using probes - a Kubernetes
        diagnostics mechanism to check the health and status of containers. Use the
        [`spec.pmm.readinessProbes.*`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pmmreadinessprobesinitialdelayseconds)
        and [`spec.pmm.livenessProbes.*`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pmmlivenessprobesinitialdelayseconds)
        Custom Resource options to fine-tune Readiness and Liveness probes for PMM
        Client.\n\n##### Improved observability of binary log backups\n\nGet insights
        into the success and failure rates of binlog operations, timeliness of processing
        and uploads and potential gaps or inconsistencies in binlog data with the
        Prometheus metrics added for the Operator. Gather this data by connecting
        to the `<pitr-pod-service>:8080/metrics` endpoint. Learn more about the available
        metrics in the [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/backups-pitr.html#binary-logs-statistics).\n\n####
        Deprecation, Rename and Removal\n\nThe `spec.haproxy.exposePrimary.enabled`
        field is deprecated. If enabled via the `spec.haproxy.enabled`, the HAProxy
        primary service is already exposed.\n\n#### New Features\n\n- [K8SPXC-747](https://perconadev.atlassian.net/browse/K8SPXC-747),
        [K8SPXC-1473](https://perconadev.atlassian.net/browse/K8SPXC-1473) - Add the
        ability to access the statistics pages for HAProxy and ProxySQL\n\n- [K8SPXC-1366](https://perconadev.atlassian.net/browse/K8SPXC-1366)
        - Add the ability to queue backups and run them sequentially, and to optimize
        the cluster load with the ability to suspend backups for an unhealthy cluster.
        A user can assign the start time and suspension time to backups to manage
        them better.\n\n- [K8SPXC-1432](https://perconadev.atlassian.net/browse/K8SPXC-1432)
        - Enable users to configure cluster-wide Operator deployments in OpenShift
        certified catalog using OLM.\n\n#### Improvements\n\n- [K8SPXC-1367](https://perconadev.atlassian.net/browse/K8SPXC-1367)
        - Now a user can configure Readiness and Liveness probes for PMM Client container
        to check its health and status\n\n- [K8SPXC-1461](https://perconadev.atlassian.net/browse/K8SPXC-1461)
        - Improve logging for resizing PVC with the information about successful and
        failed PVC resize. Log errors on resize attempts if the Storage Class doesn't
        support resizing.\n\n- [K8SPXC-1466](https://perconadev.atlassian.net/browse/K8SPXC-1466)
        - Mark the containers that provide the service as default ones with the annotation.
        This enables a user to connect to a Pod without explicitly specifying a container.\n\n-
        [K8SPXC-1473](https://perconadev.atlassian.net/browse/K8SPXC-1473) - Add the
        ability to connect to the built-in statistics pages for HAProxy and ProxySQL
        by exposing the ports for those pages\n\n- [K8SPXC-1475](https://perconadev.atlassian.net/browse/K8SPXC-1475)
        - Update the backup image to use AWS CLI instead of MinIO CLI due to the license
        change\n\n- [K8SPXC-1510](https://perconadev.atlassian.net/browse/K8SPXC-1510)
        - Add the ability to suppress messages about the use of deprecated features
        in MySQL Error Log by adding the `log_error_suppression_list` key from the
        `my.cnf` configuration file and defining the message number in the `spec.pxc.configuration`
        subsection of the Custom Resource manifest. See [how to change MySQL options](https://docs.percona.com/percona-operator-for-mysql/pxc/options.html)
        for steps. This improves readability for MySQL error log.\n\n- [K8SPXC-1512](https://perconadev.atlassian.net/browse/K8SPXC-1512)
        - For Percona XtraDB Cluster version 8.4 and above, binary log user defined
        functions for point-in-time recovery (`binlog_utils_udf`) are now installed
        as a component instead of a plugin. This improves their compatibility across
        platforms and provides automatic dependency handling.\n\n- [K8SPXC-1542](https://perconadev.atlassian.net/browse/K8SPXC-1542)
        - Improve binlog upload for large files to Azure blob storage with the ability
        to define the block size and the number of concurrent writers for the upload
        (Thanks to user dcaputo-harmoni for contribution)\n\n- [K8SPXC-1543](https://perconadev.atlassian.net/browse/K8SPXC-1543)
        - Set PITR controller reference for binlog-collector deployment the same way
        as it's set for PXC and proxy StatefulSets. This creates a connection between
        PITR deployment and cluster resource (Thank you Vlad Gusev for the contribution)\n\n-
        [K8SPXC-1544](https://perconadev.atlassian.net/browse/K8SPXC-1544) - Improve
        observability of binlog collector by adding the support of basic Prometheus
        metrics (Thank you Vlad Gusev for the contribution)\n\n- [K8SPXC-1567](https://perconadev.atlassian.net/browse/K8SPXC-1567)
        - N\n\n</details>\n\n---\n\n### Configuration\n\n\U0001F4C5 **Schedule**:
        Branch creation - At any time (no schedule defined), Automerge - At any time
        (no schedule defined).\n\n\U0001F6A6 **Automerge**: Disabled by config. Please
        merge this manually once you are satisfied.\n\n\u267B **Rebasing**: Whenever
        PR becomes conflicted, or you tick the rebase/retry checkbox.\n\n\U0001F47B
        **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://redirect.github.com/renovatebot/renovate/discussions)
        if that's undesired.\n\n---\n\n - [ ] <!-- rebase-check -->If you want to
        rebase/retry this PR, check this box\n\n---\n\nThis PR was generated by [Mend
        Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/vexxhost/atmosphere).\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4yNjQuMCIsInVwZGF0ZWRJblZlciI6IjQyLjg1LjEiLCJ0YXJnZXRCcmFuY2giOiJzdGFibGUvMjAyMy4xIiwibGFiZWxzIjpbInNraXAtcmVsZWFzZS1ub3RlcyJdfQ==-->\n"
      change_url: https://github.com/vexxhost/atmosphere/pull/2595
      child_jobs: []
      commit_id: 5d635ae7d201989f087661c6356a3703e1026788
      event_id: 6ef92260-f582-11f0-80cf-1808d8ce6c67
      executor:
        hostname: 3a2793d2bd32
        inventory_file: /var/lib/zuul/builds/2c7fba1b9702407b8b5b36b8cc9d33dd/ansible/inventory.yaml
        log_root: /var/lib/zuul/builds/2c7fba1b9702407b8b5b36b8cc9d33dd/work/logs
        result_data_file: /var/lib/zuul/builds/2c7fba1b9702407b8b5b36b8cc9d33dd/work/results.json
        src_root: /var/lib/zuul/builds/2c7fba1b9702407b8b5b36b8cc9d33dd/work/src
        work_root: /var/lib/zuul/builds/2c7fba1b9702407b8b5b36b8cc9d33dd/work
      include_vars: []
      items:
      - branch: stable/2023.1
        change: '2595'
        change_message: "Update pxc (stable/2023.1)\n\n> \u2139\uFE0F **Note**\n>
          \n> This PR body was truncated due to platform limits.\n\nThis PR contains
          the following updates:\n\n| Package | Type | Update | Change | [Age](https://docs.renovatebot.com/merge-confidence/)
          | [Confidence](https://docs.renovatebot.com/merge-confidence/) |\n|---|---|---|---|---|---|\n|
          docker.io/percona/haproxy |  | patch | `2.8.14` \u2192 `2.8.18` | ![age](https://developer.mend.io/api/mc/badges/age/docker/docker.io%2fpercona%2fhaproxy/2.8.18?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/docker.io%2fpercona%2fhaproxy/2.8.14/2.8.18?slim=true)
          |\n| docker.io/percona/percona-xtradb-cluster-operator |  | minor | `1.17.0`
          \u2192 `1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/docker/docker.io%2fpercona%2fpercona-xtradb-cluster-operator/1.19.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/docker.io%2fpercona%2fpercona-xtradb-cluster-operator/1.17.0/1.19.0?slim=true)
          |\n| [github.com/percona/percona-xtradb-cluster-operator](https://redirect.github.com/percona/percona-xtradb-cluster-operator)
          | require | minor | `v1.16.1` \u2192 `v1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fpercona%2fpercona-xtradb-cluster-operator/v1.19.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fpercona%2fpercona-xtradb-cluster-operator/v1.16.1/v1.19.0?slim=true)
          |\n| [percona/percona-xtradb-cluster-operator](https://redirect.github.com/percona/percona-xtradb-cluster-operator)
          |  | minor | `1.17.0` \u2192 `1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/github-releases/percona%2fpercona-xtradb-cluster-operator/1.19.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/github-releases/percona%2fpercona-xtradb-cluster-operator/1.17.0/1.19.0?slim=true)
          |\n| [pxc-operator](https://docs.percona.com/percona-operator-for-mysql/pxc/)
          ([source](https://redirect.github.com/percona/percona-helm-charts)) |  |
          minor | `1.17.0` \u2192 `1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/helm/pxc-operator/1.19.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/helm/pxc-operator/1.17.0/1.19.0?slim=true)
          |\n| quay.io/prometheus/mysqld-exporter |  | minor | `v0.17.0` \u2192 `v0.18.0`
          | ![age](https://developer.mend.io/api/mc/badges/age/docker/quay.io%2fprometheus%2fmysqld-exporter/v0.18.0?slim=true)
          | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/quay.io%2fprometheus%2fmysqld-exporter/v0.17.0/v0.18.0?slim=true)
          |\n\n---\n\n### Release Notes\n\n<details>\n<summary>percona/percona-xtradb-cluster-operator
          (github.com/percona/percona-xtradb-cluster-operator)</summary>\n\n### [`v1.19.0`](https://redirect.github.com/percona/percona-xtradb-cluster-operator/releases/tag/v1.19.0)\n\n[Compare
          Source](https://redirect.github.com/percona/percona-xtradb-cluster-operator/compare/v1.18.0...v1.19.0)\n\n#####
          Release Highlights\n\nThis release of Percona Operator for MySQL based on
          Percona XtraDB Cluster includes the following new features and improvements:\n\n#####
          Ensure data security for Percona XtraDB Cluster 8.4 with data-at-rest encryption\n\nData
          at rest encryption ensures that sensitive information stored on disk remains
          protected from unauthorized access, even if the physical media is compromised.
          It is a foundational safeguard for compliance, trust and security in modern
          database environments.\n\nThe Operator supports data at rest encryption
          for MySQL 8.0 with HashiCorp Vault using the `keyring_vault` *plugin*. Now,
          it also supports data at rest encryption for MySQL 8.4, leveraging the `keyring_vault`
          *component*.\n\nThis enhancement enables you to benefit from the rich feature
          set of the latest major version of Percona XtraDB Cluster 8.4 while ensuring
          your sensitive data is secured. In doing so, you can meet compliance requirements
          and protect critical information without added operational complexity. Learn
          how to [configure data at rest encryption for Percona XtraDB Cluster 8.4](https://docs.percona.com/percona-operator-for-mysql/pxc/encryption-setup.html).\n\n#####
          Percona XtraDB Cluster 8.4 is now fully supported\n\nPercona XtraDB Cluster
          8.4 is now fully supported and recommended for production deployments. Starting
          with this release, it becomes the default version for all new database cluster
          deployments using the Operator. This support enables you to benefit from
          its latest features, performance improvements, and enhanced security.\n\n#####
          Use your own CA certificates for TLS verification\n\nYou can now use your
          organization\u2019s custom Certificate Authority (CA) to securely verify
          TLS communication with S3 storage during backups and restores.\n\nThe configuration
          is straightforward: create the Secret that stores your custom CA and certificates
          to authorize in the S3 storage. Then reference this Secret and specify the
          CA certificate in the `caBundle` option in the Operator Custom Resource.
          The Operator will verify TLS communication against it.\n\nHere's the example
          configuration:\n\n```yml\nstorages:\n  minio-s3:\n    type: s3\n    verifyTLS:
          true\n    s3:\n      caBundle:\n         name: minio-ca-bundle\n         key:
          tls.crt\n```\n\nWith this improvement, you ensure the following:\n\n- Security
          without compromise \u2013 no more bypassing identity checks.\n- Alignment
          with your internal standards \u2013 use the CA your company already trusts.\n-
          Confidence in backup and restore flows \u2013 every S3 interaction is properly
          verified.\n\nRead more about the use of own CA certificates in our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/backups-storage.html#configure-tls-verification-with-custom-certificates-for-s3-storage)\n\n#####
          Configure duration for certificates issued by cert-manager\n\nBy default,
          the `cert-manager` generates certificates valid for 90 days. You now have
          more control over certificate lifetimes and can configure their custom duration
          when you create a new cluster. This way you can align with your organization's
          security and compliance policies.\n\nUse the following Custom Resource options
          to configure certificate duration:\n\n- `.spec.tls.certValidityDuration`
          \u2013 validity period for generated certificates\n- `.spec.tls.caValidityDuration`
          \u2013 validity period for the Certificate Authority (CA)\n\n```yaml\n  tls:\n
          \   enabled: true\n    certValidityDuration: 2160h\n    caValidityDuration:
          26280h\n```\n\nNote that the Operator enforces minimum durations to certificates:\n\n-
          For TLS certificates \u2013 1 hour\n- For CA certificate \u2013 730 hours.\n\nAlso,
          we don't recommend setting duration to exactly 1 hour to prevent certificate
          generation issues. Read more about rules and limitations about certificate
          duration configuration in our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/tls-cert-manager.html#customize-certificate-duration-for-cert-manager).\n\nThis
          improvement empowers you to fine-tune certificate lifetimes while keeping
          your cluster secure and stable.\n\n##### Security context for ProxySQL sidecar
          containers\n\nYou can now define the security context for ProxySQL sidecar
          containers in the Operator, reducing the risk of unsecured sidecars bypassing
          Pod restrictions. This improvement lets you set user IDs, privileges, and
          filesystem access directly, ensuring compliance and strengthening Pod security.\n\nConfigure
          the security context in your custom resource. For example:\n\n```yaml\nspec:\n
          \ proxysql:\n       sidecars:\n          securityContext:\n              privileged:
          false\n```\n\nWith this change, you enforce safer defaults across your deployments
          and close security gaps at the Pod level.\n\n##### Improved load balancing
          with ProxySQL scheduler (tech preview)\n\nThe Operator now integrates with
          the external `pxc_scheduler_handler` tool to improve query routing. This
          feature is currently in tech preview, so we recommend experimenting with
          it in test or staging environments before using it in production.\n\nWith
          this scheduler you get finer control over how your SQL queries are routed
          within your PXC cluster:\n\n- SELECT queries (that don't use FOR UPDATE)
          are intelligently distributed across all PXC nodes\u2014or all nodes except
          the writer, depending on your settings.\n- Non-SELECT queries and SELECT
          FOR UPDATE statements are routed to the writer node.\n- You don't have to
          micromanage the writer role: the scheduler automatically ensures only one
          writer is active at any time.\n\nThis means you could see:\n\n- better performance
          and higher throughput from distributing query loads\n- greater reliability
          with no single point of failure\n\n* Improved cluster health through early
          detection of replication lag and node issues\n\n- more efficient use of
          your resources and hardware\n- a smoother, more predictable experience for
          everyone using the database\n\nSee our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/proxysql-conf.html#proxysql-scheduler-tech-preview)
          for full information about the scheduler behavior and setup.\n\nThe previous
          internal scheduler remains enabled by default to maintain backward compatibility.
          You can switch to the new one when you're ready to benefit from smarter
          query handling.\n\n##### Customize HAProxy backend health check intervals
          and failover behavior\n\nYou can now control how quickly HAProxy detects
          and reacts to node failures. Instead of waiting the default 20 seconds while
          HAProxy performs the failover, you can tune health checks to cut that down
          to just a few seconds. That means your applications recover faster, and
          users don't get stuck with hanging sessions when a node goes down.\n\nYou
          no longer need to override the entire HAProxy configuration to achieve this
          \u2014 the operator now gives you simple, direct options in the Custom Resource
          specification:\n\n```yaml\nhaproxy:  \n   healthCheck:\n       interval:
          10000\n       rise: 1\n       fall: 2\n```\n\nBy adjusting how often checks
          run and how many failures or successes mark a node as \u201Cdown\u201D or
          \u201Cup,\u201D you get faster failover, cleaner client handling, and easier
          configuration that is safe to upgrade and tailored to your environment.\n\n#####
          Switch from HAProxy to ProxySQL at runtime\n\nYou can now switch from HAProxy
          to ProxySQL without redeploying your Percona XtraDB Cluster. Previously,
          you had to choose ProxySQL only at startup. Now ProxySQL has the `caching_sha2_password`
          as the default authentication plugin, which gives you the flexibility to
          start with HAProxy and migrate to ProxySQL later as your needs evolve.\n\nWith
          this release, ProxySQL also includes a new [scheduler](#improved-load-balancing-with-proxysql-scheduler-tech-preview)
          that enhances SQL awareness, automates read/write splitting, and handles
          failovers more intelligently. This leads to faster queries, increased reliability,
          and more efficient cluster resource usage.\n\n**Which proxy should you choose?**\n\n-
          **HAProxy:** Choose HAProxy if you need a lightweight, TCP-level load balancer
          with minimal configuration. Note that for read/write splitting, your clients
          must connect to different HAProxy ports based on the query type.\n- **ProxySQL:**
          Opt for ProxySQL if you want built-in read/write splitting, advanced query-level
          control, and automated failover logic right out of the box.\n\nEach proxy
          brings its own resource requirements and advantages. We offer [additional
          guidance](https://docs.percona.com/percona-operator-for-mysql/pxc/load-balancing.html#what-load-balancer-to-use)
          on selecting the right proxy for your environment, plus [detailed recommendations](https://docs.percona.com/percona-operator-for-mysql/pxc/proxy-switching.html)
          on resource planning and best practices. Review these carefully to ensure
          your choice fits your operational and performance needs.\n\nTo switch between
          proxies, update your Custom Resource to set `haproxy.enabled` to `false`
          and `proxysql.enabled` to `true`. Apply the changes, and the Operator will
          handle the transition for you by restarting the relevant proxy Pods.\n\nWith
          this improvement you now control your proxy choice at runtime, and ProxySQL
          brings smarter routing and resilience right into the Operator.\n\n#####
          ProxySQL 3 support\n\nYou can now deploy ProxySQL 3 with Percona Operator
          for MySQL. This gives you more flexibility and control over how your applications
          connect to MySQL inside Kubernetes. Here\u2019s what you get:\n\n- Dual\u2011password
          support enables you to introduce a new password while the old one is still
          valid. As a result, you can rotate passwords without downtime\n- Enhanced
          event and query logging gives you real\u2011time visibility into query behavior
          and application traffic.\n- ProxySQL now logs the actual values bound to
          prepared statements. This helps you debug queries more effectively, since
          you see what data was passed instead of just placeholders\n- Event logs
          now include metadata about ProxySQL version and format. This makes it easier
          to track and audit logs across upgrades in your Operator\u2011managed deployments.\n\n#####
          Direct-access backups: Improved performance and reliability with sidecars
          (tech preview)\n\nBy default, the Operator makes backups using the SST method.
          This creates a separate backup Pod with Percona XtraBackup, while the database
          node enters Donor state and stops serving client requests. SST backups can
          also fail with cryptic network errors, making root cause analysis and recovery
          difficult.\n\nStarting with version 1.19.0, you can make backups via the
          XtraBackup sidecar container. The Operator deploys a sidecar with XtraBackup
          inside each Percona XtraDB Cluster Pod. This sidecar makes a backup and
          uploads it to the remote backup storage. The database Pod doesn\u2019t change
          its state to Donor and keeps accepting client requests.\n\nUsing the sidecar
          method provides a direct access to data thus boosting backup performance.
          The sidecar container constantly runs in the database Pod, so you have constant
          access to logs and status, which simplifies troubleshooting.\n\nTo enable
          the XtraBackup sidecar container backup method, set `PXCO_FEATURE_GATES=XtrabackupSidecar=true`
          environment variable in the Operator Deployment.\nThis functionality is
          in the tech preview stage and currently supports only cloud storages. We
          encourage you to try it out in your testing or staging environments and
          leave your feedback.\n\nFuture enhancements such as support of PVC volumes,
          backup encryption and incremental backups are planned for future releases.\n\nTo
          learn more about XtraBackup sidecar container backup method, see our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/backups.html#xtrabackup-sidecar-method-tech-preview).\n\n#####
          Ensure only up to date data is served during backups\n\nWhen a node donates
          data during backups or SST, it enters into the DONOR state. At this point,
          the node should no longer handle client connections. HAProxy's external
          check correctly blocked new connections to the Donor node but allowed existing
          sessions to remain active. Those lingering sessions could return slow or
          outdated results.\n\nThe HAProxy default configuration now includes the
          `on-marked-down shutdown-sessions` directive. As soon as HAProxy marks a
          node as down, all active connections are immediately closed and clients
          reconnect to remaining active nodes. This ensures that only fresh, up to
          date data is served during backups.\n\n##### Automatic cleanup of backup
          and restore Jobs and associated Pods\n\nThe Operator creates a dedicated
          Job and Pod for every backup and restore operation. Previously, these Jobs
          and Pods remained in the cluster even after the operation was finished,
          and you had to manually delete them to free up resources.\n\nNow, you can
          offload this task to the Operator. Specify a time-to-live (TTL) for backup
          and restore Jobs once the operation is finished. When the TTL expires, the
          Operator automatically deletes the Job and its associated Pod.\n\nModify
          your Custom Resource as follows:\n\n```yaml\nbackup:\n  image: perconalab/percona-xtradb-cluster-operator:main-pxc8.0-backup\n
          \ ttlSecondsAfterFinished: 3600\n```\n\nThis setting is global. It applies
          to all on-demand and scheduled backups, and all restores.\n\nThe Operator
          also ensures reliability: if a backup or restore takes longer than the configured
          TTL, it applies the `internal.percona.com/keep-job` finalizer to allow the
          operation to finish. After the operation completes either with the `Succeeded`
          or the `Failed` status, the finalizer is removed and the Job is cleaned
          up.\n\nThis improvement reduces manual maintenance overhead, gives you control
          over the processes lifetime for debugging or auditing purposes and helps
          keep your cluster healthy and efficient. By reducing unnecessary resource
          buildup, you gain smoother operations, lower maintenance overhead and improved
          reliability in production environments.\n\n##### Improved backup identification
          for point-in-time recovery readiness\n\nWhen a backup contains binlog gaps,
          the Operator now creates a `<backup-name>.pitr-not-ready` file in the backup
          storage. This file makes it easy to identify which backups are appropriate
          for point in time recovery both in the storage and when listing backup objects.\n\nBefore
          starting a restore, the Operator checks for this marker file and blocks
          unsafe restores, protecting you from incomplete recovery attempts. If needed,
          you can override this safeguard by adding the `percona.com/unsafe-pitr`
          annotation to the Restore object. Use this override with caution, as this
          is an unsafe configuration.\n\n##### Attach external PVCs for shared data
          access across applications and the database cluster\n\nSometimes your database
          needs more than its own internal storage. For example, it needs access to
          reference files, shared configuration files or lookup tables generated outside
          the database but still essential for queries and procedures.\n\nYou can
          now attach auxiliary pre-existing PVCs and mount that external data directly
          into your database, ProxySQL or HAProxy pods in a clean, declarative way
          using the Custom Resource.\n\nThis example configuration shows how to attach
          external PVC to the XtraDB Cluster Pods:\n\n```yaml\npxc:\n  extraPVCs:\n
          \   - name: extra-data-volume\n      claimName: my-extra-storage\n      mountPath:
          /var/lib/mysql-extra\n      readOnly: false\n```\n\nThis improvement gives
          you a reliable way to separate internal database storage from external domain
          data, update shared datasets independently, and still benefit from the Operator\u2019s
          automation and resilience.\n\n##### Customize password generation by the
          Operator\n\nBy default, the Operator generates user passwords using alphanumeric
          characters plus a set of special symbols. Some tools such as MySQL Prometheus
          Exporter or mysqlsh don't support certain symbols, which can make those
          passwords invalid.\n\nTo improve compatibility and user experience, you
          can now customize password generation parameters in the Custom Resource:\n\n```yaml\nspec:\n
          passwordGenerationOptions:\n   symbols: \"!#$%&()*+,-.<=>?@&#8203;[]^_{}~\"\n
          \  maxLength: 20\n   minLength: 16\n```\n\nThis enhancement lets you keep
          the convenience of automated password generation and at the same time ensure
          compliance with the tools and environments you integrate with the Operator.\n\n#####
          Configure memory allocator in the Operator\n\nBy default, Percona Operator
          for XtraDB Cluster uses the system allocator (`libc`) to manage memory.
          While this works for most cases, alternative allocators such as `jemalloc`
          and `tcmalloc` can improve performance and reduce fragmentation in high-traffic
          workloads.\n\nTo have more flexibility, you can now configure the memory
          allocator directly in the Custom Resource:\n\n```yaml\nspec:\n   pxc:\n
          \    mysqlAllocator: jemalloc\n```\n\nSupported values are:\n\n- `jemalloc`\n-
          `tcmalloc`\n- `libc` (default, used when no value is set)\n\nIf you have
          already configured the memory allocator via the environment variable, the
          Operator will respect that setting and use it instead of the Custom Resource
          value.\n\nThis enhancement lets you fine-tune memory management for your
          cluster while keeping compatibility with existing configurations.\n\n#####
          Deprecation, rename, removal\n\n**Removed in 1.19.0:**\n\n- `proxysql.readinessDelaySec`
          and `proxysql.livenessDelaySec` fields are removed as redundant\n\n**Deprecated
          (will be removed in 1.22.0):**\n\n- `pxc.livenessDelaySec`. Use [`pxc.livenessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pxclivenessprobesinitialdelayseconds)\n-
          `pxc.readinessDelaySec`. Use [`pxc.readinessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pxcreadinessprobesinitialdelayseconds)\n-
          `haproxy.livenessDelaySec`. Use [`haproxy.livenessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#haproxylivenessprobesinitialdelayseconds)\n-
          `haproxy.readinessDelaySec`. Use [`haproxy.readinessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#haproxyreadinessprobesinitialdelayseconds)\n\n#####
          Changelog\n\n##### New Features\n\n- [K8SPXC-1332](https://perconadev.atlassian.net/browse/K8SPXC-1332)
          - Added the ability to load custom SSL certificates for backup operations
          to S3 storage. This enables secure communication with S3-compatible storage
          using the certificates approved and trusted by your company (Thank you Azam
          Abdoelbasier for submitting this request).\n- [K8SPXC-1494](https://perconadev.atlassian.net/browse/K8SPXC-1494)
          - Added the ability to configure the duration of TLS certificates created
          by `cert-manager`. This allows users to customize certificate lifecycles
          to meet their specific security requirements.\n- [K8SPXC-1576](https://perconadev.atlassian.net/browse/K8SPXC-1576)
          - Added the ability to use the XtraBackup sidecar container instead of SST
          for creating backups. This provides an alternative, potentially more efficient
          backup method.\n- [K8SPXC-1688](https://perconadev.atlassian.net/browse/K8SPXC-1688)
          - Added ability to mount pre-existing auxiliary PVCs as volumes to database
          and proxy pods. This facilitates easier integration with external data and
          storage resources (Thank you Emin AKTAS for submitting the request and contributing
          to it).\n- [K8SPXC-1733](https://perconadev.atlassian.net/browse/K8SPXC-1733)
          - Added the ability to customize password generation parameters, such as
          length and character sets via the Custom Resource. This ensures smooth operation
          of the tools with specific requirements towards password and leverages the
          automatic password generation of the Operator (Thank you user fydrah for
          submitting the request and contributing to it).\n- [K8SPXC-1734](https://perconadev.atlassian.net/browse/K8SPXC-1734)
          - Introduced configurable HAProxy backend health check parameters that can
          be tuned without overriding the entire configuration. This simplifies performance
          tuning for high-availability setups (Thank you Tim Stoop for submitting
          the request and contributing to it).\n\n##### Improvements\n\n- [K8SPXC-735](https://perconadev.atlassian.net/browse/K8SPXC-735)
          - Added the support of the `pxc_scheduler_handler` ProxySQL scheduler for
          SQL-aware routing and effective read/write splitting. This allows for better
          utilization of resources by distributing read-only traffic across the entire
          cluster while routing write requests only to the writer node.\n- [K8SPXC-992](https://perconadev.atlassian.net/browse/K8SPXC-992)
          - Improved binlog naming to prevent potential collisions between different
          collectors. The updated naming convention ensures unique and consistent
          identification of binary log files in storage.\n- [K8SPXC-1144](https://perconadev.atlassian.net/browse/K8SPXC-1144)
          - Introduced a mechanism to mark S3 backups as PITR-unready if binlog gaps
          are detected. This prevents users from attempting invalid point-in-time
          recoveries using inconsistent backups.\n- [K8SPXC-1214](https://perconadev.atlassian.net/browse/K8SPXC-1214)
          - Added an option to automatically clean up completed backup and restore
          jobs and their associated pods. This improvement helps reduce pressure on
          the Kubernetes API by removing stale resources (Thank you Alexandre Barth
          for reporting this issue).\n- [K8SPXC-1319](https://perconadev.atlassian.net/browse/K8SPXC-1319)
          - Enhanced the operator to support running multiple backup restores for
          different clusters in parallel. This removes a previous limitation that
          blocked concurrent restore operations across the environment.\n- [K8SPXC-1327](https://perconadev.atlassian.net/browse/K8SPXC-1327)
          - Added the ability to change the memory allocator for MySQL to improve
          memory management efficiency. This change helps optimize the overall memory
          footprint of PXC pods.\n- [K8SPXC-1373](https://perconadev.atlassian.net/browse/K8SPXC-1373)
          - Improved core dump handling to ensure that crashed instances can recover
          more reliably after an SST. This enhancement aids in diagnosing and recovering
          from unexpected server failures.\n- [K8SPXC-1431](https://perconadev.atlassian.net/browse/K8SPXC-1431)
          - Improved the delete-backup finalizer logic to correctly handle the deletion
          of on-demand backup PVCs.\n- [K8SPXC-1470](https://perconadev.atlassian.net/browse/K8SPXC-1470)
          - Added the ability to switch between HAProxy and ProxySQL within an existing
          cluster. This provides users with more flexibility to change their load-balancing
          solution as their needs evolve.\n- [K8SPXC-1511](https://perconadev.atlassian.net/browse/K8SPXC-1511)
          - Added the support of data at rest encryption for Percona XtraDB Cluster
          8.4 via the `keyring vault` component. This change ensures compatibility
          with the latest security architecture of MySQL 8.4.\n- [K8SPXC-1525](https://perconadev.atlassian.net/browse/K8SPXC-1525)
          - Deprecated `pxc.livenessDelaySec` option in favor of more consistent liveness
          probe parameters. The Operator now prioritizes standard probe configurations
          to manage Pod lifecycle.\n- [K8SPXC-1568](https://perconadev.atlassian.net/browse/K8SPXC-1568)
          - Updated the Operator's password generation logic to prevent the '\\*'
          character from being used as the first character. This avoids potential
          issues with certain authentication plugins and command-line tools.\n- [K8SPXC-1594](https://perconadev.atlassian.net/browse/K8SPXC-1594)
          - Improved the database upgrade logic to prevent the controller from being
          blocked during the operation. This ensures that the Operator remains responsive
          to other cluster changes while an upgrade is in progress.\n- [K8SPXC-1628](https://perconadev.atlassian.net/browse/K8SPXC-1628)
          - Added support for `tcmalloc` as an alternative memory allocator in PXC
          images. This gives users additional options to tune and reduce the memory
          footprint of their database workloads.\n- [K8SPXC-1647](https://perconadev.atlassian.net/browse/K8SPXC-1647)
          - Implemented extended exit codes for garbd to provide better diagnostic
          information for different failure scenarios. This helps users identify the
          root cause of SST and joining issues faster.\n- [K8SPXC-1668](https://perconadev.atlassian.net/browse/K8SPXC-1668)
          - Added support for ProxySQL 3, providing users with access to the latest
          features and performance improvements of the load balancer.\n- [K8SPXC-1683](https://perconadev.atlassian.net/browse/K8SPXC-1683)
          - Expanded smart update tests to include PXC 8.4 and PMM 3, ensuring stable
          upgrade paths for the latest versions.\n- [K8SPXC-1703](https://perconadev.atlassian.net/browse/K8SPXC-1703)
          - Added the support of the `generateEmbeddedObjectMeta` option, improving
          the template handling for sidecars and extra PVCs (Thank you Emin AKTAS
          for reporting and contributing to this issue).\n- [K8SPXC-1748](https://perconadev.atlassian.net/browse/K8SPXC-1748)
          - Eliminated runtime CREATE FUNCTION statements in the PITR collector to
          avoid unnecessary Galera TOI (Total Order Isolation) events. This reduces
          the performance impact on the cluster when the PITR sidecar starts or restarts.\n\n#####
          Bugs Fixed\n\n- [K8SPXC-926](https://perconadev.atlassian.net/browse/K8SPXC-926)
          - Fixed an issue where a failed smart update on one cluster could block
          the Operator from managing other clusters in multi-cluster environments.
          The controller now handles update failures more gracefully without impacting
          independent resources.\n- [K8SPXC-1379](https://perconadev.atlassian.net/browse/K8SPXC-1379)
          - Fixed an issue where monit container resource values in ProxySQL pods
          did not correctly reflect the values specified in the PXC cluster definition.
          The operator now ensures that ProxySQL resource attributes are properly
          applied to the monitoring sidecar containers.\n- [K8SPXC-1424](https://perconadev.atlassian.net/browse/K8SPXC-1424)
          - Resolved a certificate renewal issue where CA certificates in TLS secrets
          could expire before server certificates were renewed. The Operator logic
          was updated to align renewal intervals for CA and server certificates when
          using cert-manager.\n- [K8SPXC-1581](https://perconadev.atlassian.net/browse/K8SPXC-1581)
          - Corrected the order of options in the restore prepare job to ensure that
          `--defaults-file` is passed as the first option to xtrabackup. This fix
          ensures that custom configuration files are correctly prioritized during
          the restore process.\n- [K8SPXC-1617](https://perconadev.atlassian.net/browse/K8SPXC-1617)
          - Fixed a binlog gap issue in Point-in-Time Recovery (PITR) that caused
          repeated test failures. Users are now advised to perform a full backup after
          each PITR restore to ensure data consistency and prevent gaps.\n- [K8SPXC-1632](https://perconadev.atlassian.net/browse/K8SPXC-1632)
          - Added missing SecurityContext configurations for ProxySQL sidecar containers
          to enhance pod security. This change ensures that all sidecars follow the
          defined security standards of the cluster.\n- [K8SPXC-1655](https://perconadev.atlassian.net/browse/K8SPXC-1655)
          - Fixed a failure in xtrabackup when using LZ4 compression on RHEL9-based
          Percona XtraDB Cluster images. The fix addresses compatibility issues with
          the latest compression libraries in the operating system environment.\n-
          [K8SPXC-1686](https://perconadev.atlassian.net/browse/K8SPXC-1686) - Improved
          backup error handling to ensure that providing an invalid Percona XtraBackup
          image results in a failed status. A new timeout field was introduced to
          prevent backup objects from hanging indefinitely in a starting state.\n-
          [K8SPXC-1687](https://perconadev.atlassian.net/browse/K8SPXC-1687) - Fixed
          the `copy-backup.sh` script to correctly handle and copy cloud-based backups
          stored in S3 or Azure. This ensures that the utility script works consistently
          across all supported storage types.\n- [K8SPXC-1701](https://perconadev.atlassian.net/browse/K8SPXC-1701)
          - Ensured that MySQL configurations are correctly mounted to the restore
          prepare job. This fix allows the restore process to use custom MySQL settings
          defined in the cluster (Thank you Emin AKTAS for reporting and contributing
          to this issue).\n- [K8SPXC-1702](https://perconadev.atlassian.net/browse/K8SPXC-1702)
          - Added the ability to override time zones for backup jobs. This resolves
          issues where time-dependent operations could fail due to missing timezone
          definitions (Thank you Emin AKTAS for reporting and contributing to this
          issue).\n- [K8SPXC-1721](https://perconadev.atlassian.net/browse/K8SPXC-1721)
          - Added a sleep interval to the recovery loop to prevent high CPU usage
          spikes when containers restart.\n- [K8SPXC-1725](https://perconadev.atlassian.net/browse/K8SPXC-1725)
          - Fixed a condition where a cluster could return stalled data during a backup
          or SST operation by adding the on-marked-down shutdown-sessions directive
          to HAProxy default configuration. This ensures that only fresh, up to date
          data is served during backups.\n- [K8SPXC-1726](https://perconadev.atlassian.net/browse/K8SPXC-1726)
          - Resolved a deployment breakage in the Operator version 1.18.0 via Helm
          caused by PMM 3 client incompatibilities. The fix ensures a smoother upgrade
          path for users migrating to newer versions of PMM (Thank you Antonio Falzarano
          for reporting and contributing to this issue).\n- [K8SPXC-1760](https://perconadev.atlassian.net/browse/K8SPXC-1760)
          - Fixed the handling of the crVersion field in the Helm chart templates.
          The Operator now correctly considers the version defined in `values.yaml`
          when generating the cluster configuration.\n- [K8SPXC-1771](https://perconadev.atlassian.net/browse/K8SPXC-1771)
          - Fixed the issue with excessive logging by the backup controller when backups
          are suspended or resumed due to an unready cluster. This improves log readability
          and reduces unnecessary diagnostic noise.\n- [K8SPXC-1772](https://perconadev.atlassian.net/browse/K8SPXC-1772)
          - Fixed a state transition bug where unsuspended backups could move directly
          from 'Starting' to 'Succeeded' without entering the 'Running' state. This
          ensures accurate tracking and visibility of the backup process status.\n\n#####
          Documentation Improvements\n\n- [K8SPXC-1747](https://perconadev.atlassian.net/browse/K8SPXC-1747)
          - Improved the documentation with the information about available environment
          variables for cluster components and the Operator. Documented the `S3_WORKERS_LIMIT`
          environment variable to allow throttling of backup deletions.\n- [K8SPXC-1661](https://perconadev.atlassian.net/browse/K8SPXC-1661)
          - Updated the operator documentation to reflect that PMM 3 uses service
          accounts instead of API keys. This ensures that users can correctly configure
          monitoring integration with the latest versions of PMM.\n- [K8SPXC-1663](https://perconadev.atlassian.net/browse/K8SPXC-1663)
          - Improved documentation for Point-in-Time Recovery steps. The updated documentation
          properly separates and sequences the recovery instructions for improved
          readability.\n\n##### Supported Software\n\nThe Operator was developed and
          tested with the following software:\n\n- Percona XtraDB Cluster versions
          8.4.7-7.1, 8.0.44-35.1, and 5.7.44-31.65\n- Percona XtraBackup versions
          8.4.0-5.1, 8.0.35-34.1, and 2.4.29\n- HAProxy 2.8.17\n- ProxySQL 2.7.3-1.2,
          3.0.1-1.2\n- LogCollector based on fluent-bit 4.0.1-1\n- PMM Client 2.44.1-1
          and 3.5.0\n\nOther options may also work but have not been tested.\n\n#####
          Supported Platforms\n\nPercona Operators are designed for compatibility
          with all [CNCF-certified](https://www.cncf.io/training/certification/software-conformance/)
          Kubernetes distributions. Our release process includes targeted testing
          and validation on major cloud provider platforms and OpenShift, as detailed
          below:\n\n- [Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine)
          1.31 - 1.33\n- [Amazon Elastic Container Service for Kubernetes (EKS)](https://aws.amazon.com)
          1.32 - 1.34\n- [Azure Kubernetes Service (AKS)](https://azure.microsoft.com/en-us/services/kubernetes-service/)
          1.32 - 1.34\n- [OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift)
          4.17 - 4.20\n- [Minikube](https://minikube.sigs.k8s.io/docs/) 1.37.0 based
          on Kubernetes 1.34.0\n\nThis 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.\n\n### [`v1.18.0`](https://redirect.github.com/percona/percona-xtradb-cluster-operator/releases/tag/v1.18.0)\n\n[Compare
          Source](https://redirect.github.com/percona/percona-xtradb-cluster-operator/compare/v1.17.0...v1.18.0)\n\n#####
          Release Highlights\n\nThis release of Percona Operator for MySQL based on
          Percona XtraDB Cluster includes the following new features and improvements:\n\n#####
          PMM3 support\n\nThe Operator is natively integrated with [PMM 3](https://www.percona.com/doc/percona-monitoring-and-management/3/index.html),
          enabling you to monitor the health and performance of your Percona Distribution
          for MySQL deployment and at the same time enjoy enhanced performance, new
          features, and improved security that PMM 3 provides.\n\nNote that the Operator
          supports both PMM2 and PMM3. The decision on what PMM version is used depends
          on the authentication method you provide in the Operator configuration:
          PMM2 uses API keys while PMM3 uses service account token. If the Operator
          configuration contains both authentication methods with non-empty values,
          PMM3 takes the priority.\n\nTo use PMM, ensure that the PMM client image
          is compatible with the PMM Server version. Check [Percona certified images](https://docs.percona.com/percona-operator-for-mysql/pxc/images.html)
          for the correct client image.\n\nFor how to configure monitoring with PMM,
          see the [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/monitoring.html).\n\n#####
          Improved monitoring for clusters in multi-region or multi-namespace deployments
          in PMM\n\nNow you can define a custom name for your clusters deployed in
          different data centers. This name helps Percona Management and Monitoring
          (PMM) Server to correctly recognize clusters as connected and monitor them
          as one deployment. Similarly, PMM Server identifies clusters deployed with
          the same names in different namespaces as separate ones and correctly displays
          performance metrics for you on dashboards.\n\nTo assign a custom name, define
          this configuration in the Custom Resource manifest for your cluster:\n\n```yaml\nspec:\n
          \ pmm:\n    customClusterName: testClusterName\n```\n\n##### More resilient
          database restores without matching user Secrets\n\nYou no longer need matching
          user Secrets between your backup and your target cluster to perform a restore.
          The Operator now has a post-restore step that changes user passwords in
          the restored database to the ones from the local Secret. Also, it creates
          missing system users and adds missing grants.\n\nThis flow is the same regardless
          of whether you restore to the same cluster or to a completely new one.\n\nThe
          removal of this major roadblock to have a Secret for restores makes your
          disaster recovery process smoother and more reliable. This enhancement makes
          managing databases on Kubernetes more robust and operator-friendly.\n\n#####
          Improved backup retention for streamlined management of scheduled backups
          in cloud storage\n\nA new backup retention configuration gives you more
          control over how backups are managed in storage and retained in Kubernetes.\n\nWith
          the `deleteFromStorage` flag , you can disable automatic deletion from AWS
          S3 or Azure Blob storage and instead rely on native cloud lifecycle policies.
          This makes backup cleanup more efficient and better aligned with flexible
          storage strategies.\n\nThe legacy `keep` option is now deprecated and mapped
          to the new `retention` block for compatibility. We encourage you to start
          using the `backup.schedule.retention` configuration:\n\n```yaml\nschedule:\n
          \ - name: \"sat-night-backup\"\n    schedule: \"0 0 * * 6\"\n    retention:\n
          \     count: 3\n      type: count\n      deleteFromStorage: true\n    storageName:
          s3-us-west\n```\n\nNote that if you have both `backup.schedule.keep`  and
          `backup.schedule.retention`  defined, the `backup.schedule.retention` takes
          precedence.\n\n##### Added labels to identify the version of the Operator\n\nCustom
          Resource Definition (CRD) is compatible with the last three Operator versions.
          To know which Operator version is attached to it, we've added labels to
          all Custom Resource Definitions. The labels help you identify the current
          Operator version and decide if you need to update the CRD. To view the labels,
          run: `kubectl get crd perconaxtradbclusters.pxc.percona.com --show-labels`.\n\n#####
          Cross-site replication is now supported for Percona XtraDB Cluster 8.4\n\nCross-site
          replication is now available with Percona XtraDB Cluster 8.4.x, lifting
          one of the  limitations in the Operator for this database version. This
          enhancement marks a significant step toward general availability of Percona
          XtraDB Cluster 8.4 in the Operator by enabling multi-site deployments and
          improving resilience across distributed environments.\n\n##### Deprecation,
          Rename and Removal\n\n- The `pxc.expose.loadBalancerIP`, `haproxy.exposePrimary.loadBalancerIP`,
          `haproxy.exposeReplicas.loadBalancerIP` and `proxysql.expose.loadBalancerIP`
          keys are deprecated. The `loadBalancerIP` field is also deprecated upstream
          in Kubernetes\n  due to its inconsistent behavior across cloud providers
          and lack of dual-stack support. As a result, its usage is strongly discouraged.\n\n
          \ We recommend using cloud provider-specific annotations instead, as they
          offer more predictable and portable behavior for managing load balancer
          IP assignments.\n\n  The `pxc.expose.loadBalancerIP`, `haproxy.exposePrimary.loadBalancerIP`,
          `haproxy.exposeReplicas.loadBalancerIP` and `proxysql.expose.loadBalancerIP`
          keys are scheduled for removal in future releases.\n\n- The `backup.schedule.keep`
          field is deprecated and will be removed after release 1.21.0. We recommend
          using the `backup.schedule.retention` instead as follows:\n\n  ```yaml\n
          \ schedule:\n    - name: \"sat-night-backup\"\n      schedule: \"0 0 **
          6\"\n      retention:\n        count: 3\n        type: count\n        deleteFromStorage:
          true\n      storageName: s3-us-west\n  ```\n\n- New repositories for Percona
          XtraBackup and Logcollector\n\n  Now the Operator uses the official Percona
          Docker images for the `percona-xtrabackup` and `logcollector` components.
          Pay attention to the new image repositories when you upgrade the Operator
          and the database. Check the [Percona certified images](https://docs.percona.com/percona-operator-for-mysql/pxc/images.html)
          for exact image names.\n\n- Changes for Helm charts:\n\n  - PMM3 is now
          the default. To keep using PMM2, set the `pmm.tag: 2.44.1`\n  - If you install
          or upgrade the Operator with default manifests using Helm charts on Openshift
          4.19, you must use the `docker.io` registry prefix to guarantee successful
          download from the DockerHub `percona-xtradb-cluster` repository. Read the
          [Considerations for using OpenShift 4.19](#considerations-for-using-openshift-419)
          section for more information.\n\n##### Known limitations\n\n##### Considerations
          for using OpenShift 4.19\n\nStarting with OpenShift 4.19, the way images
          with not fully qualified names are pulled has changed for repositories that
          share the same repository name on DockerHub and Red Hat Marketplace. By
          default the tags are pulled from Red Hat Marketplace. Specifying not fully
          qualified image names may result in the `ImagePullBackOff` error.\n\n- **OLM
          installation:** Images are provided with the fully qualified names and are
          pulled from the Red Hat Marketplace/DockerHub registry.\n- **Manual install/update
          with default manifests:** Images must use the `docker.io` registry prefix
          to guarantee successful download from the Dockerhub `percona-xtradb-cluster`
          repository.\n\nSee our documentation for [manual installation](https://docs.percona.com/percona-operator-for-mysql/pxc/openshift.html#install-the-operator-via-the-command-line-interface)
          or [update](https://docs.percona.com/percona-operator-for-mysql/pxc/update_openshift.html#update-via-the-command-line-interface).\n\n#####
          Changleog\n\n##### New Features\n\n- [K8SPXC-1284](https://perconadev.atlassian.net/browse/K8SPXC-1284)
          - Add the ability to configure protocol for peer-list DNS SRV lookups\n\n-
          [K8SPXC-1599](https://perconadev.atlassian.net/browse/K8SPXC-1599) - Allowed
          setting `loadBalancerClass` service type and using a custom implementation
          of a load balancer rather than the cloud provider default one\n\n##### Improvements\n\n-
          [K8SPXC-1375](https://perconadev.atlassian.net/browse/K8SPXC-1375) - Added
          a new retention configuration to allow users to delegate backup cleanup
          to cloud lifecycle policies (Thank you user Tristan for reporting this issue)\n\n-
          [K8SPXC-1376](https://perconadev.atlassian.net/browse/K8SPXC-1376) - Added
          the ability to restore from backup without a matching Secret resource\n\n-
          [K8SPXC-1399](https://perconadev.atlassian.net/browse/K8SPXC-1399) - Added
          a documentation how to set up a disaster recovery system and transfer workloads
          between sites\n\n- [K8SPXC-1415](https://perconadev.atlassian.net/browse/K8SPXC-1415)
          - Updated the `percona-xtrabackup` image to use the official `percona-xtrabackup`
          Docker image\n\n- [K8SPXC-1430](https://perconadev.atlassian.net/browse/K8SPXC-1430)
          - Improved handling of autogenerated certificates depending on the `delete-ssl`
          finalizer configuration\n\n- [K8SPXC-1448](https://perconadev.atlassian.net/browse/K8SPXC-1448),
          [K8SPXC-1449](https://perconadev.atlassian.net/browse/K8SPXC-1449) - Improved
          the `pvc-resize` test by using a custom storage class for EKS, reducing
          errors and improving the quota handling during resize\n\n- [K8SPXC-1450](https://perconadev.atlassian.net/browse/K8SPXC-1450)
          - Improved PVC resizing behavior when reducing the storage size by reverting
          the values when the quota is reached\n\n- [K8SPXC-1472](https://perconadev.atlassian.net/browse/K8SPXC-1472)
          - Deprecated the `loadBalancerIP` field due to its deprecation upstream\n\n-
          [K8SPXC-1513](https://perconadev.atlassian.net/browse/K8SPXC-1513) - Added
          PXC 8.4 support for version service\n\n- [K8SPXC-1529](https://perconadev.atlassian.net/browse/K8SPXC-1529)
          - Added support for cross-site replication with MySQL 8.4.0 by adding the
          use of `authentication_policy` instead of `default_authentication_plugin`\n\n-
          [K8SPXC-1553](https://perconadev.atlassian.net/browse/K8SPXC-1553) - Added
          support for PMM v3\n\n- [K8SPXC-1560](https://perconadev.atlassian.net/browse/K8SPXC-1560)
          - Added the warning about CRDs not being upgraded automatically after helm
          upgrade to the output\n\n- [K8SPXC-1566](https://perconadev.atlassian.net/browse/K8SPXC-1566)
          - Improved reconciliation of replicationChannels without proxy Pods by starting
          the database Pod bypassing the proxy (Thank you Justin Reasoner for contributing
          to this issue)\n\n- [K8SPXC-1569](https://perconadev.atlassian.net/browse/K8SPXC-1569)
          - Added Labels for Custom Resource Definitions (CRD) to identify the Operator
          version attached to them\n\n- [K8SPXC-1597](https://perconadev.atlassian.net/browse/K8SPXC-1597)
          - Improve the scheduled backups behavior for a cluster in an unhealthy state
          by postponing the job until the cluster reports the healthy status\n\n-
          [K8SPXC-1605](https://perconadev.atlassian.net/browse/K8SPXC-1605) - Introduced
          Azure CLI for checking if backup objects/folders exist in Azure storage\n\n-
          [K8SPXC-1612](https://perconadev.atlassian.net/browse/K8SPXC-1612) - Added
          the `imagePullSecrets` for PMM image\n\n- [K8SPXC-1615](https://perconadev.atlassian.net/browse/K8SPXC-1615)
          - Added the ability to define a custom cluster name for `pmm-admin` component\n\n-
          [K8SPXC-1624](https://perconadev.atlassian.net/browse/K8SPXC-1624) - Deleted
          deprecated finalizers code\n\n- [K8SPXC-1669](https://perconadev.atlassian.net/browse/K8SPXC-1669)
          - Improve the backup flow by generating a default endpoint URL for a storage
          from a region if it is not provided (Thank you Bernard Grymonpon for reporting
          this issue)\n\n- [K8SPXC-1677](https://perconadev.atlassian.net/browse/K8SPXC-1677)
          - Document the changed behavior with pulling images for default manifests
          on OpenShift 4.19 and update install and update instructions\n\n##### Bugs
          Fixed\n\n- [K8SPXC-1312](https://perconadev.atlassian.net/browse/K8SPXC-1312)
          - Fixed the issue with labels not being updated automatically for point-in-time
          recovery deployment upon Custom Resource changes\n\n- [K8SPXC-1347](https://perconadev.atlassian.net/browse/K8SPXC-1347)
          - Fixed the issue with point-in-time recovery failing due to TLS configuration
          mismatch between the server and the point-in-time recovery job by configuring
          it to use TLS if is required by the server.\n\n- [K8SPXC-1382](https://perconadev.atlassian.net/browse/K8SPXC-1382)
          - Fixed the issue with backup failing on AWS if using IAM profile without
          credentialsSecret by using credentialsSecret only when explicitly specified
          and relying on IAM roles instead (Thank you Itiel Olenick for reporting
          this issue)\n\n- [K8SPXC-1541](https://perconadev.atlassian.net/browse/K8SPXC-1541)
          - Fixed Telemetry module to to consider both empty string \"\" and comma
          separated namespaces in cluster-wide mode\n\n- [K8SPXC-1548](https://perconadev.atlassian.net/browse/K8SPXC-1548)
          Fixed the issue with deleting old backups on Google Cloud Storage by url-decoding
          the object path before deleting it (Thank you Mateusz Gruszkiewicz for reporting
          this issue)\n\n- [K8SPXC-1631](https://perconadev.atlassian.net/browse/K8SPXC-1631)
          - Fixed the issue with the Operator restarting pod-0 after the cluster is
          ready. The issue is caused by ConfigMap and StatefulSet being created too
          close to each other and Kubernetes API can't return the newly created ConfigMap
          before creating the StatefulSet. The issue is fixed by reconciling the StatefulSet
          after the reconciliation of ConfigMap is completed.\n\n- [K8SPXC-1664](https://perconadev.atlassian.net/browse/K8SPXC-1664)
          - Fixed the use of the proper script to check PXC nodes when adding them
          by HAProxy\n\n##### Supported Software\n\nThe Operator was developed and
          tested with the following software:\n\n- Percona XtraDB Cluster versions
          8.4.5-5.1 (Tech preview), 8.0.42-33.1, and 5.7.44-31.65\n- Percona XtraBackup
          versions 8.4.0-3, 8.0.35-34.1, and 2.4.29\n- HAProxy 2.8.15-1\n- ProxySQL
          2.7.3\n- LogCollector based on fluent-bit 4.0.1\n- PMM Client 2.44.1 and
          3.3.1\n\nOther options may also work but have not been tested.\n\n#####
          Supported Platforms\n\nPercona Operators are designed for compatibility
          with all [CNCF-certified](https://www.cncf.io/training/certification/software-conformance/)
          Kubernetes distributions. Our release process includes targeted testing
          and validation on major cloud provider platforms and OpenShift, as detailed
          below for Operator version 1.16.0:\n\n- [Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine)
          1.30 - 1.33\n- [Amazon Elastic Container Service for Kubernetes (EKS)](https://aws.amazon.com)
          1.30 - 1.33\n- [Azure Kubernetes Service (AKS)](https://azure.microsoft.com/en-us/services/kubernetes-service/)
          1.30 - 1.33\n- [OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift)
          4.15 - 4.19\n- [Minikube](https://minikube.sigs.k8s.io/docs/) 1.36.0 based
          on Kubernetes 1.33.1\n\nThis 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.\n\n### [`v1.17.0`](https://redirect.github.com/percona/percona-xtradb-cluster-operator/releases/tag/v1.17.0)\n\n[Compare
          Source](https://redirect.github.com/percona/percona-xtradb-cluster-operator/compare/v1.16.1...v1.17.0)\n\n####
          Release Highlights\n\n##### Improved observability for HAProxy and ProxySQL\n\nGet
          insights into the HAProxy and ProxySQL performance by connecting to their
          statistics pages. Use the `cluster-name-haproxy:8084` and `cluster-name-proxysql:6070`
          endpoints to do so. Learn about other available ports in the [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/haproxy-conf.html).\n\n#####
          Improved cluster load management during backups\n\nIf parallel backups overload
          your cluster, you can turn off parallel execution to prevent this. Previously,
          this meant that you could only run one backup at a time - no new backups
          could start until the current one was finished. Now, the Operator queues
          backups and runs them one after another automatically. You can fine-tune
          the backup sequence by setting the start time for all backups or for a specific
          on-demand one using the [`spec.backup.startingDeadlineSeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#backupstartingdeadlineseconds)
          Custom Resource option. This provides greater control over backup operations.\n\nAnother
          improvement is for the case when your database cluster becomes unhealthy,
          for example, when a Pod crashes or restarts. The Operator suspends running
          backups to reduce the cluster's load. Once the cluster recovers and reports
          a Ready status, the Operator resumes the suspended backup. To further offload
          the cluster during an unhealthy state, you can configure how long a backup
          remains suspended by using the [`spec.backup.suspendedDeadlineSeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#backupsuspendeddeadlineseconds)
          Custom Resource option. If this time expires before the cluster recovers,
          the backup is marked as \"failed.\"\n\n##### Monitor PMM Client health and
          status\n\nPercona Monitoring and Management (PMM) is a great tool to [monitor
          the health of your database cluster](https://docs.percona.com/percona-operator-for-mysql/pxc/monitoring.html).
          Now you can also learn if PMM itself is healthy using probes - a Kubernetes
          diagnostics mechanism to check the health and status of containers. Use
          the [`spec.pmm.readinessProbes.*`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pmmreadinessprobesinitialdelayseconds)
          and [`spec.pmm.livenessProbes.*`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pmmlivenessprobesinitialdelayseconds)
          Custom Resource options to fine-tune Readiness and Liveness probes for PMM
          Client.\n\n##### Improved observability of binary log backups\n\nGet insights
          into the success and failure rates of binlog operations, timeliness of processing
          and uploads and potential gaps or inconsistencies in binlog data with the
          Prometheus metrics added for the Operator. Gather this data by connecting
          to the `<pitr-pod-service>:8080/metrics` endpoint. Learn more about the
          available metrics in the [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/backups-pitr.html#binary-logs-statistics).\n\n####
          Deprecation, Rename and Removal\n\nThe `spec.haproxy.exposePrimary.enabled`
          field is deprecated. If enabled via the `spec.haproxy.enabled`, the HAProxy
          primary service is already exposed.\n\n#### New Features\n\n- [K8SPXC-747](https://perconadev.atlassian.net/browse/K8SPXC-747),
          [K8SPXC-1473](https://perconadev.atlassian.net/browse/K8SPXC-1473) - Add
          the ability to access the statistics pages for HAProxy and ProxySQL\n\n-
          [K8SPXC-1366](https://perconadev.atlassian.net/browse/K8SPXC-1366) - Add
          the ability to queue backups and run them sequentially, and to optimize
          the cluster load with the ability to suspend backups for an unhealthy cluster.
          A user can assign the start time and suspension time to backups to manage
          them better.\n\n- [K8SPXC-1432](https://perconadev.atlassian.net/browse/K8SPXC-1432)
          - Enable users to configure cluster-wide Operator deployments in OpenShift
          certified catalog using OLM.\n\n#### Improvements\n\n- [K8SPXC-1367](https://perconadev.atlassian.net/browse/K8SPXC-1367)
          - Now a user can configure Readiness and Liveness probes for PMM Client
          container to check its health and status\n\n- [K8SPXC-1461](https://perconadev.atlassian.net/browse/K8SPXC-1461)
          - Improve logging for resizing PVC with the information about successful
          and failed PVC resize. Log errors on resize attempts if the Storage Class
          doesn't support resizing.\n\n- [K8SPXC-1466](https://perconadev.atlassian.net/browse/K8SPXC-1466)
          - Mark the containers that provide the service as default ones with the
          annotation. This enables a user to connect to a Pod without explicitly specifying
          a container.\n\n- [K8SPXC-1473](https://perconadev.atlassian.net/browse/K8SPXC-1473)
          - Add the ability to connect to the built-in statistics pages for HAProxy
          and ProxySQL by exposing the ports for those pages\n\n- [K8SPXC-1475](https://perconadev.atlassian.net/browse/K8SPXC-1475)
          - Update the backup image to use AWS CLI instead of MinIO CLI due to the
          license change\n\n- [K8SPXC-1510](https://perconadev.atlassian.net/browse/K8SPXC-1510)
          - Add the ability to suppress messages about the use of deprecated features
          in MySQL Error Log by adding the `log_error_suppression_list` key from the
          `my.cnf` configuration file and defining the message number in the `spec.pxc.configuration`
          subsection of the Custom Resource manifest. See [how to change MySQL options](https://docs.percona.com/percona-operator-for-mysql/pxc/options.html)
          for steps. This improves readability for MySQL error log.\n\n- [K8SPXC-1512](https://perconadev.atlassian.net/browse/K8SPXC-1512)
          - For Percona XtraDB Cluster version 8.4 and above, binary log user defined
          functions for point-in-time recovery (`binlog_utils_udf`) are now installed
          as a component instead of a plugin. This improves their compatibility across
          platforms and provides automatic dependency handling.\n\n- [K8SPXC-1542](https://perconadev.atlassian.net/browse/K8SPXC-1542)
          - Improve binlog upload for large files to Azure blob storage with the ability
          to define the block size and the number of concurrent writers for the upload
          (Thanks to user dcaputo-harmoni for contribution)\n\n- [K8SPXC-1543](https://perconadev.atlassian.net/browse/K8SPXC-1543)
          - Set PITR controller reference for binlog-collector deployment the same
          way as it's set for PXC and proxy StatefulSets. This creates a connection
          between PITR deployment and cluster resource (Thank you Vlad Gusev for the
          contribution)\n\n- [K8SPXC-1544](https://perconadev.atlassian.net/browse/K8SPXC-1544)
          - Improve observability of binlog collector by adding the support of basic
          Prometheus metrics (Thank you Vlad Gusev for the contribution)\n\n- [K8SPXC-1567](https://perconadev.atlassian.net/browse/K8SPXC-1567)
          - N\n\n</details>\n\n---\n\n### Configuration\n\n\U0001F4C5 **Schedule**:
          Branch creation - At any time (no schedule defined), Automerge - At any
          time (no schedule defined).\n\n\U0001F6A6 **Automerge**: Disabled by config.
          Please merge this manually once you are satisfied.\n\n\u267B **Rebasing**:
          Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.\n\n\U0001F47B
          **Immortal**: This PR will be recreated if closed unmerged. Get [config
          help](https://redirect.github.com/renovatebot/renovate/discussions) if that's
          undesired.\n\n---\n\n - [ ] <!-- rebase-check -->If you want to rebase/retry
          this PR, check this box\n\n---\n\nThis PR was generated by [Mend Renovate](https://mend.io/renovate/).
          View the [repository job log](https://developer.mend.io/github/vexxhost/atmosphere).\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4yNjQuMCIsInVwZGF0ZWRJblZlciI6IjQyLjg1LjEiLCJ0YXJnZXRCcmFuY2giOiJzdGFibGUvMjAyMy4xIiwibGFiZWxzIjpbInNraXAtcmVsZWFzZS1ub3RlcyJdfQ==-->\n"
        change_url: https://github.com/vexxhost/atmosphere/pull/2595
        commit_id: 5d635ae7d201989f087661c6356a3703e1026788
        patchset: 5d635ae7d201989f087661c6356a3703e1026788
        project:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/atmosphere
          name: vexxhost/atmosphere
          short_name: atmosphere
          src_dir: src/github.com/vexxhost/atmosphere
        topic: null
      job: atmosphere-molecule-csi-local-path-provisioner
      jobtags: []
      max_attempts: 3
      message: Update pxc (stable/2023.1)

> ℹ️ **Note**
> 
> This PR body was truncated due to platform limits.

This PR contains the following updates:

| Package | Type | Update | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|---|---|
| docker.io/percona/haproxy |  | patch | `2.8.14` → `2.8.18` | ![age](https://developer.mend.io/api/mc/badges/age/docker/docker.io%2fpercona%2fhaproxy/2.8.18?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/docker.io%2fpercona%2fhaproxy/2.8.14/2.8.18?slim=true) |
| docker.io/percona/percona-xtradb-cluster-operator |  | minor | `1.17.0` → `1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/docker/docker.io%2fpercona%2fpercona-xtradb-cluster-operator/1.19.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/docker.io%2fpercona%2fpercona-xtradb-cluster-operator/1.17.0/1.19.0?slim=true) |
| [github.com/percona/percona-xtradb-cluster-operator](https://redirect.github.com/percona/percona-xtradb-cluster-operator) | require | minor | `v1.16.1` → `v1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fpercona%2fpercona-xtradb-cluster-operator/v1.19.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fpercona%2fpercona-xtradb-cluster-operator/v1.16.1/v1.19.0?slim=true) |
| [percona/percona-xtradb-cluster-operator](https://redirect.github.com/percona/percona-xtradb-cluster-operator) |  | minor | `1.17.0` → `1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/github-releases/percona%2fpercona-xtradb-cluster-operator/1.19.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/github-releases/percona%2fpercona-xtradb-cluster-operator/1.17.0/1.19.0?slim=true) |
| [pxc-operator](https://docs.percona.com/percona-operator-for-mysql/pxc/) ([source](https://redirect.github.com/percona/percona-helm-charts)) |  | minor | `1.17.0` → `1.19.0` | ![age](https://developer.mend.io/api/mc/badges/age/helm/pxc-operator/1.19.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/helm/pxc-operator/1.17.0/1.19.0?slim=true) |
| quay.io/prometheus/mysqld-exporter |  | minor | `v0.17.0` → `v0.18.0` | ![age](https://developer.mend.io/api/mc/badges/age/docker/quay.io%2fprometheus%2fmysqld-exporter/v0.18.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/quay.io%2fprometheus%2fmysqld-exporter/v0.17.0/v0.18.0?slim=true) |

---

### Release Notes

<details>
<summary>percona/percona-xtradb-cluster-operator (github.com/percona/percona-xtradb-cluster-operator)</summary>

### [`v1.19.0`](https://redirect.github.com/percona/percona-xtradb-cluster-operator/releases/tag/v1.19.0)

[Compare Source](https://redirect.github.com/percona/percona-xtradb-cluster-operator/compare/v1.18.0...v1.19.0)

##### Release Highlights

This release of Percona Operator for MySQL based on Percona XtraDB Cluster includes the following new features and improvements:

##### Ensure data security for Percona XtraDB Cluster 8.4 with data-at-rest encryption

Data at rest encryption ensures that sensitive information stored on disk remains protected from unauthorized access, even if the physical media is compromised. It is a foundational safeguard for compliance, trust and security in modern database environments.

The Operator supports data at rest encryption for MySQL 8.0 with HashiCorp Vault using the `keyring_vault` *plugin*. Now, it also supports data at rest encryption for MySQL 8.4, leveraging the `keyring_vault` *component*.

This enhancement enables you to benefit from the rich feature set of the latest major version of Percona XtraDB Cluster 8.4 while ensuring your sensitive data is secured. In doing so, you can meet compliance requirements and protect critical information without added operational complexity. Learn how to [configure data at rest encryption for Percona XtraDB Cluster 8.4](https://docs.percona.com/percona-operator-for-mysql/pxc/encryption-setup.html).

##### Percona XtraDB Cluster 8.4 is now fully supported

Percona XtraDB Cluster 8.4 is now fully supported and recommended for production deployments. Starting with this release, it becomes the default version for all new database cluster deployments using the Operator. This support enables you to benefit from its latest features, performance improvements, and enhanced security.

##### Use your own CA certificates for TLS verification

You can now use your organization’s custom Certificate Authority (CA) to securely verify TLS communication with S3 storage during backups and restores.

The configuration is straightforward: create the Secret that stores your custom CA and certificates to authorize in the S3 storage. Then reference this Secret and specify the CA certificate in the `caBundle` option in the Operator Custom Resource. The Operator will verify TLS communication against it.

Here's the example configuration:

```yml
storages:
  minio-s3:
    type: s3
    verifyTLS: true
    s3:
      caBundle:
         name: minio-ca-bundle
         key: tls.crt
```

With this improvement, you ensure the following:

- Security without compromise – no more bypassing identity checks.
- Alignment with your internal standards – use the CA your company already trusts.
- Confidence in backup and restore flows – every S3 interaction is properly verified.

Read more about the use of own CA certificates in our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/backups-storage.html#configure-tls-verification-with-custom-certificates-for-s3-storage)

##### Configure duration for certificates issued by cert-manager

By default, the `cert-manager` generates certificates valid for 90 days. You now have more control over certificate lifetimes and can configure their custom duration when you create a new cluster. This way you can align with your organization's security and compliance policies.

Use the following Custom Resource options to configure certificate duration:

- `.spec.tls.certValidityDuration` – validity period for generated certificates
- `.spec.tls.caValidityDuration` – validity period for the Certificate Authority (CA)

```yaml
  tls:
    enabled: true
    certValidityDuration: 2160h
    caValidityDuration: 26280h
```

Note that the Operator enforces minimum durations to certificates:

- For TLS certificates – 1 hour
- For CA certificate – 730 hours.

Also, we don't recommend setting duration to exactly 1 hour to prevent certificate generation issues. Read more about rules and limitations about certificate duration configuration in our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/tls-cert-manager.html#customize-certificate-duration-for-cert-manager).

This improvement empowers you to fine-tune certificate lifetimes while keeping your cluster secure and stable.

##### Security context for ProxySQL sidecar containers

You can now define the security context for ProxySQL sidecar containers in the Operator, reducing the risk of unsecured sidecars bypassing Pod restrictions. This improvement lets you set user IDs, privileges, and filesystem access directly, ensuring compliance and strengthening Pod security.

Configure the security context in your custom resource. For example:

```yaml
spec:
  proxysql:
       sidecars:
          securityContext:
              privileged: false
```

With this change, you enforce safer defaults across your deployments and close security gaps at the Pod level.

##### Improved load balancing with ProxySQL scheduler (tech preview)

The Operator now integrates with the external `pxc_scheduler_handler` tool to improve query routing. This feature is currently in tech preview, so we recommend experimenting with it in test or staging environments before using it in production.

With this scheduler you get finer control over how your SQL queries are routed within your PXC cluster:

- SELECT queries (that don't use FOR UPDATE) are intelligently distributed across all PXC nodes—or all nodes except the writer, depending on your settings.
- Non-SELECT queries and SELECT FOR UPDATE statements are routed to the writer node.
- You don't have to micromanage the writer role: the scheduler automatically ensures only one writer is active at any time.

This means you could see:

- better performance and higher throughput from distributing query loads
- greater reliability with no single point of failure

* Improved cluster health through early detection of replication lag and node issues

- more efficient use of your resources and hardware
- a smoother, more predictable experience for everyone using the database

See our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/proxysql-conf.html#proxysql-scheduler-tech-preview) for full information about the scheduler behavior and setup.

The previous internal scheduler remains enabled by default to maintain backward compatibility. You can switch to the new one when you're ready to benefit from smarter query handling.

##### Customize HAProxy backend health check intervals and failover behavior

You can now control how quickly HAProxy detects and reacts to node failures. Instead of waiting the default 20 seconds while HAProxy performs the failover, you can tune health checks to cut that down to just a few seconds. That means your applications recover faster, and users don't get stuck with hanging sessions when a node goes down.

You no longer need to override the entire HAProxy configuration to achieve this — the operator now gives you simple, direct options in the Custom Resource specification:

```yaml
haproxy:  
   healthCheck:
       interval: 10000
       rise: 1
       fall: 2
```

By adjusting how often checks run and how many failures or successes mark a node as “down” or “up,” you get faster failover, cleaner client handling, and easier configuration that is safe to upgrade and tailored to your environment.

##### Switch from HAProxy to ProxySQL at runtime

You can now switch from HAProxy to ProxySQL without redeploying your Percona XtraDB Cluster. Previously, you had to choose ProxySQL only at startup. Now ProxySQL has the `caching_sha2_password` as the default authentication plugin, which gives you the flexibility to start with HAProxy and migrate to ProxySQL later as your needs evolve.

With this release, ProxySQL also includes a new [scheduler](#improved-load-balancing-with-proxysql-scheduler-tech-preview) that enhances SQL awareness, automates read/write splitting, and handles failovers more intelligently. This leads to faster queries, increased reliability, and more efficient cluster resource usage.

**Which proxy should you choose?**

- **HAProxy:** Choose HAProxy if you need a lightweight, TCP-level load balancer with minimal configuration. Note that for read/write splitting, your clients must connect to different HAProxy ports based on the query type.
- **ProxySQL:** Opt for ProxySQL if you want built-in read/write splitting, advanced query-level control, and automated failover logic right out of the box.

Each proxy brings its own resource requirements and advantages. We offer [additional guidance](https://docs.percona.com/percona-operator-for-mysql/pxc/load-balancing.html#what-load-balancer-to-use) on selecting the right proxy for your environment, plus [detailed recommendations](https://docs.percona.com/percona-operator-for-mysql/pxc/proxy-switching.html) on resource planning and best practices. Review these carefully to ensure your choice fits your operational and performance needs.

To switch between proxies, update your Custom Resource to set `haproxy.enabled` to `false` and `proxysql.enabled` to `true`. Apply the changes, and the Operator will handle the transition for you by restarting the relevant proxy Pods.

With this improvement you now control your proxy choice at runtime, and ProxySQL brings smarter routing and resilience right into the Operator.

##### ProxySQL 3 support

You can now deploy ProxySQL 3 with Percona Operator for MySQL. This gives you more flexibility and control over how your applications connect to MySQL inside Kubernetes. Here’s what you get:

- Dual‑password support enables you to introduce a new password while the old one is still valid. As a result, you can rotate passwords without downtime
- Enhanced event and query logging gives you real‑time visibility into query behavior and application traffic.
- ProxySQL now logs the actual values bound to prepared statements. This helps you debug queries more effectively, since you see what data was passed instead of just placeholders
- Event logs now include metadata about ProxySQL version and format. This makes it easier to track and audit logs across upgrades in your Operator‑managed deployments.

##### Direct-access backups: Improved performance and reliability with sidecars (tech preview)

By default, the Operator makes backups using the SST method. This creates a separate backup Pod with Percona XtraBackup, while the database node enters Donor state and stops serving client requests. SST backups can also fail with cryptic network errors, making root cause analysis and recovery difficult.

Starting with version 1.19.0, you can make backups via the XtraBackup sidecar container. The Operator deploys a sidecar with XtraBackup inside each Percona XtraDB Cluster Pod. This sidecar makes a backup and uploads it to the remote backup storage. The database Pod doesn’t change its state to Donor and keeps accepting client requests.

Using the sidecar method provides a direct access to data thus boosting backup performance. The sidecar container constantly runs in the database Pod, so you have constant access to logs and status, which simplifies troubleshooting.

To enable the XtraBackup sidecar container backup method, set `PXCO_FEATURE_GATES=XtrabackupSidecar=true` environment variable in the Operator Deployment.
This functionality is in the tech preview stage and currently supports only cloud storages. We encourage you to try it out in your testing or staging environments and leave your feedback.

Future enhancements such as support of PVC volumes, backup encryption and incremental backups are planned for future releases.

To learn more about XtraBackup sidecar container backup method, see our [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/backups.html#xtrabackup-sidecar-method-tech-preview).

##### Ensure only up to date data is served during backups

When a node donates data during backups or SST, it enters into the DONOR state. At this point, the node should no longer handle client connections. HAProxy's external check correctly blocked new connections to the Donor node but allowed existing sessions to remain active. Those lingering sessions could return slow or outdated results.

The HAProxy default configuration now includes the `on-marked-down shutdown-sessions` directive. As soon as HAProxy marks a node as down, all active connections are immediately closed and clients reconnect to remaining active nodes. This ensures that only fresh, up to date data is served during backups.

##### Automatic cleanup of backup and restore Jobs and associated Pods

The Operator creates a dedicated Job and Pod for every backup and restore operation. Previously, these Jobs and Pods remained in the cluster even after the operation was finished, and you had to manually delete them to free up resources.

Now, you can offload this task to the Operator. Specify a time-to-live (TTL) for backup and restore Jobs once the operation is finished. When the TTL expires, the Operator automatically deletes the Job and its associated Pod.

Modify your Custom Resource as follows:

```yaml
backup:
  image: perconalab/percona-xtradb-cluster-operator:main-pxc8.0-backup
  ttlSecondsAfterFinished: 3600
```

This setting is global. It applies to all on-demand and scheduled backups, and all restores.

The Operator also ensures reliability: if a backup or restore takes longer than the configured TTL, it applies the `internal.percona.com/keep-job` finalizer to allow the operation to finish. After the operation completes either with the `Succeeded` or the `Failed` status, the finalizer is removed and the Job is cleaned up.

This improvement reduces manual maintenance overhead, gives you control over the processes lifetime for debugging or auditing purposes and helps keep your cluster healthy and efficient. By reducing unnecessary resource buildup, you gain smoother operations, lower maintenance overhead and improved reliability in production environments.

##### Improved backup identification for point-in-time recovery readiness

When a backup contains binlog gaps, the Operator now creates a `<backup-name>.pitr-not-ready` file in the backup storage. This file makes it easy to identify which backups are appropriate for point in time recovery both in the storage and when listing backup objects.

Before starting a restore, the Operator checks for this marker file and blocks unsafe restores, protecting you from incomplete recovery attempts. If needed, you can override this safeguard by adding the `percona.com/unsafe-pitr` annotation to the Restore object. Use this override with caution, as this is an unsafe configuration.

##### Attach external PVCs for shared data access across applications and the database cluster

Sometimes your database needs more than its own internal storage. For example, it needs access to reference files, shared configuration files or lookup tables generated outside the database but still essential for queries and procedures.

You can now attach auxiliary pre-existing PVCs and mount that external data directly into your database, ProxySQL or HAProxy pods in a clean, declarative way using the Custom Resource.

This example configuration shows how to attach external PVC to the XtraDB Cluster Pods:

```yaml
pxc:
  extraPVCs:
    - name: extra-data-volume
      claimName: my-extra-storage
      mountPath: /var/lib/mysql-extra
      readOnly: false
```

This improvement gives you a reliable way to separate internal database storage from external domain data, update shared datasets independently, and still benefit from the Operator’s automation and resilience.

##### Customize password generation by the Operator

By default, the Operator generates user passwords using alphanumeric characters plus a set of special symbols. Some tools such as MySQL Prometheus Exporter or mysqlsh don't support certain symbols, which can make those passwords invalid.

To improve compatibility and user experience, you can now customize password generation parameters in the Custom Resource:

```yaml
spec:
 passwordGenerationOptions:
   symbols: "!#$%&()*+,-.<=>?@&#8203;[]^_{}~"
   maxLength: 20
   minLength: 16
```

This enhancement lets you keep the convenience of automated password generation and at the same time ensure compliance with the tools and environments you integrate with the Operator.

##### Configure memory allocator in the Operator

By default, Percona Operator for XtraDB Cluster uses the system allocator (`libc`) to manage memory. While this works for most cases, alternative allocators such as `jemalloc` and `tcmalloc` can improve performance and reduce fragmentation in high-traffic workloads.

To have more flexibility, you can now configure the memory allocator directly in the Custom Resource:

```yaml
spec:
   pxc:
     mysqlAllocator: jemalloc
```

Supported values are:

- `jemalloc`
- `tcmalloc`
- `libc` (default, used when no value is set)

If you have already configured the memory allocator via the environment variable, the Operator will respect that setting and use it instead of the Custom Resource value.

This enhancement lets you fine-tune memory management for your cluster while keeping compatibility with existing configurations.

##### Deprecation, rename, removal

**Removed in 1.19.0:**

- `proxysql.readinessDelaySec` and `proxysql.livenessDelaySec` fields are removed as redundant

**Deprecated (will be removed in 1.22.0):**

- `pxc.livenessDelaySec`. Use [`pxc.livenessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pxclivenessprobesinitialdelayseconds)
- `pxc.readinessDelaySec`. Use [`pxc.readinessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pxcreadinessprobesinitialdelayseconds)
- `haproxy.livenessDelaySec`. Use [`haproxy.livenessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#haproxylivenessprobesinitialdelayseconds)
- `haproxy.readinessDelaySec`. Use [`haproxy.readinessProbes.initialDelaySeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#haproxyreadinessprobesinitialdelayseconds)

##### Changelog

##### New Features

- [K8SPXC-1332](https://perconadev.atlassian.net/browse/K8SPXC-1332) - Added the ability to load custom SSL certificates for backup operations to S3 storage. This enables secure communication with S3-compatible storage using the certificates approved and trusted by your company (Thank you Azam Abdoelbasier for submitting this request).
- [K8SPXC-1494](https://perconadev.atlassian.net/browse/K8SPXC-1494) - Added the ability to configure the duration of TLS certificates created by `cert-manager`. This allows users to customize certificate lifecycles to meet their specific security requirements.
- [K8SPXC-1576](https://perconadev.atlassian.net/browse/K8SPXC-1576) - Added the ability to use the XtraBackup sidecar container instead of SST for creating backups. This provides an alternative, potentially more efficient backup method.
- [K8SPXC-1688](https://perconadev.atlassian.net/browse/K8SPXC-1688) - Added ability to mount pre-existing auxiliary PVCs as volumes to database and proxy pods. This facilitates easier integration with external data and storage resources (Thank you Emin AKTAS for submitting the request and contributing to it).
- [K8SPXC-1733](https://perconadev.atlassian.net/browse/K8SPXC-1733) - Added the ability to customize password generation parameters, such as length and character sets via the Custom Resource. This ensures smooth operation of the tools with specific requirements towards password and leverages the automatic password generation of the Operator (Thank you user fydrah for submitting the request and contributing to it).
- [K8SPXC-1734](https://perconadev.atlassian.net/browse/K8SPXC-1734) - Introduced configurable HAProxy backend health check parameters that can be tuned without overriding the entire configuration. This simplifies performance tuning for high-availability setups (Thank you Tim Stoop for submitting the request and contributing to it).

##### Improvements

- [K8SPXC-735](https://perconadev.atlassian.net/browse/K8SPXC-735) - Added the support of the `pxc_scheduler_handler` ProxySQL scheduler for SQL-aware routing and effective read/write splitting. This allows for better utilization of resources by distributing read-only traffic across the entire cluster while routing write requests only to the writer node.
- [K8SPXC-992](https://perconadev.atlassian.net/browse/K8SPXC-992) - Improved binlog naming to prevent potential collisions between different collectors. The updated naming convention ensures unique and consistent identification of binary log files in storage.
- [K8SPXC-1144](https://perconadev.atlassian.net/browse/K8SPXC-1144) - Introduced a mechanism to mark S3 backups as PITR-unready if binlog gaps are detected. This prevents users from attempting invalid point-in-time recoveries using inconsistent backups.
- [K8SPXC-1214](https://perconadev.atlassian.net/browse/K8SPXC-1214) - Added an option to automatically clean up completed backup and restore jobs and their associated pods. This improvement helps reduce pressure on the Kubernetes API by removing stale resources (Thank you Alexandre Barth for reporting this issue).
- [K8SPXC-1319](https://perconadev.atlassian.net/browse/K8SPXC-1319) - Enhanced the operator to support running multiple backup restores for different clusters in parallel. This removes a previous limitation that blocked concurrent restore operations across the environment.
- [K8SPXC-1327](https://perconadev.atlassian.net/browse/K8SPXC-1327) - Added the ability to change the memory allocator for MySQL to improve memory management efficiency. This change helps optimize the overall memory footprint of PXC pods.
- [K8SPXC-1373](https://perconadev.atlassian.net/browse/K8SPXC-1373) - Improved core dump handling to ensure that crashed instances can recover more reliably after an SST. This enhancement aids in diagnosing and recovering from unexpected server failures.
- [K8SPXC-1431](https://perconadev.atlassian.net/browse/K8SPXC-1431) - Improved the delete-backup finalizer logic to correctly handle the deletion of on-demand backup PVCs.
- [K8SPXC-1470](https://perconadev.atlassian.net/browse/K8SPXC-1470) - Added the ability to switch between HAProxy and ProxySQL within an existing cluster. This provides users with more flexibility to change their load-balancing solution as their needs evolve.
- [K8SPXC-1511](https://perconadev.atlassian.net/browse/K8SPXC-1511) - Added the support of data at rest encryption for Percona XtraDB Cluster 8.4 via the `keyring vault` component. This change ensures compatibility with the latest security architecture of MySQL 8.4.
- [K8SPXC-1525](https://perconadev.atlassian.net/browse/K8SPXC-1525) - Deprecated `pxc.livenessDelaySec` option in favor of more consistent liveness probe parameters. The Operator now prioritizes standard probe configurations to manage Pod lifecycle.
- [K8SPXC-1568](https://perconadev.atlassian.net/browse/K8SPXC-1568) - Updated the Operator's password generation logic to prevent the '\*' character from being used as the first character. This avoids potential issues with certain authentication plugins and command-line tools.
- [K8SPXC-1594](https://perconadev.atlassian.net/browse/K8SPXC-1594) - Improved the database upgrade logic to prevent the controller from being blocked during the operation. This ensures that the Operator remains responsive to other cluster changes while an upgrade is in progress.
- [K8SPXC-1628](https://perconadev.atlassian.net/browse/K8SPXC-1628) - Added support for `tcmalloc` as an alternative memory allocator in PXC images. This gives users additional options to tune and reduce the memory footprint of their database workloads.
- [K8SPXC-1647](https://perconadev.atlassian.net/browse/K8SPXC-1647) - Implemented extended exit codes for garbd to provide better diagnostic information for different failure scenarios. This helps users identify the root cause of SST and joining issues faster.
- [K8SPXC-1668](https://perconadev.atlassian.net/browse/K8SPXC-1668) - Added support for ProxySQL 3, providing users with access to the latest features and performance improvements of the load balancer.
- [K8SPXC-1683](https://perconadev.atlassian.net/browse/K8SPXC-1683) - Expanded smart update tests to include PXC 8.4 and PMM 3, ensuring stable upgrade paths for the latest versions.
- [K8SPXC-1703](https://perconadev.atlassian.net/browse/K8SPXC-1703) - Added the support of the `generateEmbeddedObjectMeta` option, improving the template handling for sidecars and extra PVCs (Thank you Emin AKTAS for reporting and contributing to this issue).
- [K8SPXC-1748](https://perconadev.atlassian.net/browse/K8SPXC-1748) - Eliminated runtime CREATE FUNCTION statements in the PITR collector to avoid unnecessary Galera TOI (Total Order Isolation) events. This reduces the performance impact on the cluster when the PITR sidecar starts or restarts.

##### Bugs Fixed

- [K8SPXC-926](https://perconadev.atlassian.net/browse/K8SPXC-926) - Fixed an issue where a failed smart update on one cluster could block the Operator from managing other clusters in multi-cluster environments. The controller now handles update failures more gracefully without impacting independent resources.
- [K8SPXC-1379](https://perconadev.atlassian.net/browse/K8SPXC-1379) - Fixed an issue where monit container resource values in ProxySQL pods did not correctly reflect the values specified in the PXC cluster definition. The operator now ensures that ProxySQL resource attributes are properly applied to the monitoring sidecar containers.
- [K8SPXC-1424](https://perconadev.atlassian.net/browse/K8SPXC-1424) - Resolved a certificate renewal issue where CA certificates in TLS secrets could expire before server certificates were renewed. The Operator logic was updated to align renewal intervals for CA and server certificates when using cert-manager.
- [K8SPXC-1581](https://perconadev.atlassian.net/browse/K8SPXC-1581) - Corrected the order of options in the restore prepare job to ensure that `--defaults-file` is passed as the first option to xtrabackup. This fix ensures that custom configuration files are correctly prioritized during the restore process.
- [K8SPXC-1617](https://perconadev.atlassian.net/browse/K8SPXC-1617) - Fixed a binlog gap issue in Point-in-Time Recovery (PITR) that caused repeated test failures. Users are now advised to perform a full backup after each PITR restore to ensure data consistency and prevent gaps.
- [K8SPXC-1632](https://perconadev.atlassian.net/browse/K8SPXC-1632) - Added missing SecurityContext configurations for ProxySQL sidecar containers to enhance pod security. This change ensures that all sidecars follow the defined security standards of the cluster.
- [K8SPXC-1655](https://perconadev.atlassian.net/browse/K8SPXC-1655) - Fixed a failure in xtrabackup when using LZ4 compression on RHEL9-based Percona XtraDB Cluster images. The fix addresses compatibility issues with the latest compression libraries in the operating system environment.
- [K8SPXC-1686](https://perconadev.atlassian.net/browse/K8SPXC-1686) - Improved backup error handling to ensure that providing an invalid Percona XtraBackup image results in a failed status. A new timeout field was introduced to prevent backup objects from hanging indefinitely in a starting state.
- [K8SPXC-1687](https://perconadev.atlassian.net/browse/K8SPXC-1687) - Fixed the `copy-backup.sh` script to correctly handle and copy cloud-based backups stored in S3 or Azure. This ensures that the utility script works consistently across all supported storage types.
- [K8SPXC-1701](https://perconadev.atlassian.net/browse/K8SPXC-1701) - Ensured that MySQL configurations are correctly mounted to the restore prepare job. This fix allows the restore process to use custom MySQL settings defined in the cluster (Thank you Emin AKTAS for reporting and contributing to this issue).
- [K8SPXC-1702](https://perconadev.atlassian.net/browse/K8SPXC-1702) - Added the ability to override time zones for backup jobs. This resolves issues where time-dependent operations could fail due to missing timezone definitions (Thank you Emin AKTAS for reporting and contributing to this issue).
- [K8SPXC-1721](https://perconadev.atlassian.net/browse/K8SPXC-1721) - Added a sleep interval to the recovery loop to prevent high CPU usage spikes when containers restart.
- [K8SPXC-1725](https://perconadev.atlassian.net/browse/K8SPXC-1725) - Fixed a condition where a cluster could return stalled data during a backup or SST operation by adding the on-marked-down shutdown-sessions directive to HAProxy default configuration. This ensures that only fresh, up to date data is served during backups.
- [K8SPXC-1726](https://perconadev.atlassian.net/browse/K8SPXC-1726) - Resolved a deployment breakage in the Operator version 1.18.0 via Helm caused by PMM 3 client incompatibilities. The fix ensures a smoother upgrade path for users migrating to newer versions of PMM (Thank you Antonio Falzarano for reporting and contributing to this issue).
- [K8SPXC-1760](https://perconadev.atlassian.net/browse/K8SPXC-1760) - Fixed the handling of the crVersion field in the Helm chart templates. The Operator now correctly considers the version defined in `values.yaml` when generating the cluster configuration.
- [K8SPXC-1771](https://perconadev.atlassian.net/browse/K8SPXC-1771) - Fixed the issue with excessive logging by the backup controller when backups are suspended or resumed due to an unready cluster. This improves log readability and reduces unnecessary diagnostic noise.
- [K8SPXC-1772](https://perconadev.atlassian.net/browse/K8SPXC-1772) - Fixed a state transition bug where unsuspended backups could move directly from 'Starting' to 'Succeeded' without entering the 'Running' state. This ensures accurate tracking and visibility of the backup process status.

##### Documentation Improvements

- [K8SPXC-1747](https://perconadev.atlassian.net/browse/K8SPXC-1747) - Improved the documentation with the information about available environment variables for cluster components and the Operator. Documented the `S3_WORKERS_LIMIT` environment variable to allow throttling of backup deletions.
- [K8SPXC-1661](https://perconadev.atlassian.net/browse/K8SPXC-1661) - Updated the operator documentation to reflect that PMM 3 uses service accounts instead of API keys. This ensures that users can correctly configure monitoring integration with the latest versions of PMM.
- [K8SPXC-1663](https://perconadev.atlassian.net/browse/K8SPXC-1663) - Improved documentation for Point-in-Time Recovery steps. The updated documentation properly separates and sequences the recovery instructions for improved readability.

##### Supported Software

The Operator was developed and tested with the following software:

- Percona XtraDB Cluster versions 8.4.7-7.1, 8.0.44-35.1, and 5.7.44-31.65
- Percona XtraBackup versions 8.4.0-5.1, 8.0.35-34.1, and 2.4.29
- HAProxy 2.8.17
- ProxySQL 2.7.3-1.2, 3.0.1-1.2
- LogCollector based on fluent-bit 4.0.1-1
- PMM Client 2.44.1-1 and 3.5.0

Other options may also work but have not been tested.

##### Supported Platforms

Percona Operators are designed for compatibility with all [CNCF-certified](https://www.cncf.io/training/certification/software-conformance/) Kubernetes distributions. Our release process includes targeted testing and validation on major cloud provider platforms and OpenShift, as detailed below:

- [Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine) 1.31 - 1.33
- [Amazon Elastic Container Service for Kubernetes (EKS)](https://aws.amazon.com) 1.32 - 1.34
- [Azure Kubernetes Service (AKS)](https://azure.microsoft.com/en-us/services/kubernetes-service/) 1.32 - 1.34
- [OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift) 4.17 - 4.20
- [Minikube](https://minikube.sigs.k8s.io/docs/) 1.37.0 based on Kubernetes 1.34.0

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.

### [`v1.18.0`](https://redirect.github.com/percona/percona-xtradb-cluster-operator/releases/tag/v1.18.0)

[Compare Source](https://redirect.github.com/percona/percona-xtradb-cluster-operator/compare/v1.17.0...v1.18.0)

##### Release Highlights

This release of Percona Operator for MySQL based on Percona XtraDB Cluster includes the following new features and improvements:

##### PMM3 support

The Operator is natively integrated with [PMM 3](https://www.percona.com/doc/percona-monitoring-and-management/3/index.html), enabling you to monitor the health and performance of your Percona Distribution for MySQL deployment and at the same time enjoy enhanced performance, new features, and improved security that PMM 3 provides.

Note that the Operator supports both PMM2 and PMM3. The decision on what PMM version is used depends on the authentication method you provide in the Operator configuration: PMM2 uses API keys while PMM3 uses service account token. If the Operator configuration contains both authentication methods with non-empty values, PMM3 takes the priority.

To use PMM, ensure that the PMM client image is compatible with the PMM Server version. Check [Percona certified images](https://docs.percona.com/percona-operator-for-mysql/pxc/images.html) for the correct client image.

For how to configure monitoring with PMM, see the [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/monitoring.html).

##### Improved monitoring for clusters in multi-region or multi-namespace deployments in PMM

Now you can define a custom name for your clusters deployed in different data centers. This name helps Percona Management and Monitoring (PMM) Server to correctly recognize clusters as connected and monitor them as one deployment. Similarly, PMM Server identifies clusters deployed with the same names in different namespaces as separate ones and correctly displays performance metrics for you on dashboards.

To assign a custom name, define this configuration in the Custom Resource manifest for your cluster:

```yaml
spec:
  pmm:
    customClusterName: testClusterName
```

##### More resilient database restores without matching user Secrets

You no longer need matching user Secrets between your backup and your target cluster to perform a restore. The Operator now has a post-restore step that changes user passwords in the restored database to the ones from the local Secret. Also, it creates missing system users and adds missing grants.

This flow is the same regardless of whether you restore to the same cluster or to a completely new one.

The removal of this major roadblock to have a Secret for restores makes your disaster recovery process smoother and more reliable. This enhancement makes managing databases on Kubernetes more robust and operator-friendly.

##### Improved backup retention for streamlined management of scheduled backups in cloud storage

A new backup retention configuration gives you more control over how backups are managed in storage and retained in Kubernetes.

With the `deleteFromStorage` flag , you can disable automatic deletion from AWS S3 or Azure Blob storage and instead rely on native cloud lifecycle policies. This makes backup cleanup more efficient and better aligned with flexible storage strategies.

The legacy `keep` option is now deprecated and mapped to the new `retention` block for compatibility. We encourage you to start using the `backup.schedule.retention` configuration:

```yaml
schedule:
  - name: "sat-night-backup"
    schedule: "0 0 * * 6"
    retention:
      count: 3
      type: count
      deleteFromStorage: true
    storageName: s3-us-west
```

Note that if you have both `backup.schedule.keep`  and `backup.schedule.retention`  defined, the `backup.schedule.retention` takes precedence.

##### Added labels to identify the version of the Operator

Custom Resource Definition (CRD) is compatible with the last three Operator versions. To know which Operator version is attached to it, we've added labels to all Custom Resource Definitions. The labels help you identify the current Operator version and decide if you need to update the CRD. To view the labels, run: `kubectl get crd perconaxtradbclusters.pxc.percona.com --show-labels`.

##### Cross-site replication is now supported for Percona XtraDB Cluster 8.4

Cross-site replication is now available with Percona XtraDB Cluster 8.4.x, lifting one of the  limitations in the Operator for this database version. This enhancement marks a significant step toward general availability of Percona XtraDB Cluster 8.4 in the Operator by enabling multi-site deployments and improving resilience across distributed environments.

##### Deprecation, Rename and Removal

- The `pxc.expose.loadBalancerIP`, `haproxy.exposePrimary.loadBalancerIP`, `haproxy.exposeReplicas.loadBalancerIP` and `proxysql.expose.loadBalancerIP` keys are deprecated. The `loadBalancerIP` field is also deprecated upstream in Kubernetes
  due to its inconsistent behavior across cloud providers and lack of dual-stack support. As a result, its usage is strongly discouraged.

  We recommend using cloud provider-specific annotations instead, as they offer more predictable and portable behavior for managing load balancer IP assignments.

  The `pxc.expose.loadBalancerIP`, `haproxy.exposePrimary.loadBalancerIP`, `haproxy.exposeReplicas.loadBalancerIP` and `proxysql.expose.loadBalancerIP` keys are scheduled for removal in future releases.

- The `backup.schedule.keep` field is deprecated and will be removed after release 1.21.0. We recommend using the `backup.schedule.retention` instead as follows:

  ```yaml
  schedule:
    - name: "sat-night-backup"
      schedule: "0 0 ** 6"
      retention:
        count: 3
        type: count
        deleteFromStorage: true
      storageName: s3-us-west
  ```

- New repositories for Percona XtraBackup and Logcollector

  Now the Operator uses the official Percona Docker images for the `percona-xtrabackup` and `logcollector` components. Pay attention to the new image repositories when you upgrade the Operator and the database. Check the [Percona certified images](https://docs.percona.com/percona-operator-for-mysql/pxc/images.html) for exact image names.

- Changes for Helm charts:

  - PMM3 is now the default. To keep using PMM2, set the `pmm.tag: 2.44.1`
  - If you install or upgrade the Operator with default manifests using Helm charts on Openshift 4.19, you must use the `docker.io` registry prefix to guarantee successful download from the DockerHub `percona-xtradb-cluster` repository. Read the [Considerations for using OpenShift 4.19](#considerations-for-using-openshift-419) section for more information.

##### Known limitations

##### Considerations for using OpenShift 4.19

Starting with OpenShift 4.19, the way images with not fully qualified names are pulled has changed for repositories that share the same repository name on DockerHub and Red Hat Marketplace. By default the tags are pulled from Red Hat Marketplace. Specifying not fully qualified image names may result in the `ImagePullBackOff` error.

- **OLM installation:** Images are provided with the fully qualified names and are pulled from the Red Hat Marketplace/DockerHub registry.
- **Manual install/update with default manifests:** Images must use the `docker.io` registry prefix to guarantee successful download from the Dockerhub `percona-xtradb-cluster` repository.

See our documentation for [manual installation](https://docs.percona.com/percona-operator-for-mysql/pxc/openshift.html#install-the-operator-via-the-command-line-interface) or [update](https://docs.percona.com/percona-operator-for-mysql/pxc/update_openshift.html#update-via-the-command-line-interface).

##### Changleog

##### New Features

- [K8SPXC-1284](https://perconadev.atlassian.net/browse/K8SPXC-1284) - Add the ability to configure protocol for peer-list DNS SRV lookups

- [K8SPXC-1599](https://perconadev.atlassian.net/browse/K8SPXC-1599) - Allowed setting `loadBalancerClass` service type and using a custom implementation of a load balancer rather than the cloud provider default one

##### Improvements

- [K8SPXC-1375](https://perconadev.atlassian.net/browse/K8SPXC-1375) - Added a new retention configuration to allow users to delegate backup cleanup to cloud lifecycle policies (Thank you user Tristan for reporting this issue)

- [K8SPXC-1376](https://perconadev.atlassian.net/browse/K8SPXC-1376) - Added the ability to restore from backup without a matching Secret resource

- [K8SPXC-1399](https://perconadev.atlassian.net/browse/K8SPXC-1399) - Added a documentation how to set up a disaster recovery system and transfer workloads between sites

- [K8SPXC-1415](https://perconadev.atlassian.net/browse/K8SPXC-1415) - Updated the `percona-xtrabackup` image to use the official `percona-xtrabackup` Docker image

- [K8SPXC-1430](https://perconadev.atlassian.net/browse/K8SPXC-1430) - Improved handling of autogenerated certificates depending on the `delete-ssl` finalizer configuration

- [K8SPXC-1448](https://perconadev.atlassian.net/browse/K8SPXC-1448), [K8SPXC-1449](https://perconadev.atlassian.net/browse/K8SPXC-1449) - Improved the `pvc-resize` test by using a custom storage class for EKS, reducing errors and improving the quota handling during resize

- [K8SPXC-1450](https://perconadev.atlassian.net/browse/K8SPXC-1450) - Improved PVC resizing behavior when reducing the storage size by reverting the values when the quota is reached

- [K8SPXC-1472](https://perconadev.atlassian.net/browse/K8SPXC-1472) - Deprecated the `loadBalancerIP` field due to its deprecation upstream

- [K8SPXC-1513](https://perconadev.atlassian.net/browse/K8SPXC-1513) - Added PXC 8.4 support for version service

- [K8SPXC-1529](https://perconadev.atlassian.net/browse/K8SPXC-1529) - Added support for cross-site replication with MySQL 8.4.0 by adding the use of `authentication_policy` instead of `default_authentication_plugin`

- [K8SPXC-1553](https://perconadev.atlassian.net/browse/K8SPXC-1553) - Added support for PMM v3

- [K8SPXC-1560](https://perconadev.atlassian.net/browse/K8SPXC-1560) - Added the warning about CRDs not being upgraded automatically after helm upgrade to the output

- [K8SPXC-1566](https://perconadev.atlassian.net/browse/K8SPXC-1566) - Improved reconciliation of replicationChannels without proxy Pods by starting the database Pod bypassing the proxy (Thank you Justin Reasoner for contributing to this issue)

- [K8SPXC-1569](https://perconadev.atlassian.net/browse/K8SPXC-1569) - Added Labels for Custom Resource Definitions (CRD) to identify the Operator version attached to them

- [K8SPXC-1597](https://perconadev.atlassian.net/browse/K8SPXC-1597) - Improve the scheduled backups behavior for a cluster in an unhealthy state by postponing the job until the cluster reports the healthy status

- [K8SPXC-1605](https://perconadev.atlassian.net/browse/K8SPXC-1605) - Introduced Azure CLI for checking if backup objects/folders exist in Azure storage

- [K8SPXC-1612](https://perconadev.atlassian.net/browse/K8SPXC-1612) - Added the `imagePullSecrets` for PMM image

- [K8SPXC-1615](https://perconadev.atlassian.net/browse/K8SPXC-1615) - Added the ability to define a custom cluster name for `pmm-admin` component

- [K8SPXC-1624](https://perconadev.atlassian.net/browse/K8SPXC-1624) - Deleted deprecated finalizers code

- [K8SPXC-1669](https://perconadev.atlassian.net/browse/K8SPXC-1669) - Improve the backup flow by generating a default endpoint URL for a storage from a region if it is not provided (Thank you Bernard Grymonpon for reporting this issue)

- [K8SPXC-1677](https://perconadev.atlassian.net/browse/K8SPXC-1677) - Document the changed behavior with pulling images for default manifests on OpenShift 4.19 and update install and update instructions

##### Bugs Fixed

- [K8SPXC-1312](https://perconadev.atlassian.net/browse/K8SPXC-1312) - Fixed the issue with labels not being updated automatically for point-in-time recovery deployment upon Custom Resource changes

- [K8SPXC-1347](https://perconadev.atlassian.net/browse/K8SPXC-1347) - Fixed the issue with point-in-time recovery failing due to TLS configuration mismatch between the server and the point-in-time recovery job by configuring it to use TLS if is required by the server.

- [K8SPXC-1382](https://perconadev.atlassian.net/browse/K8SPXC-1382) - Fixed the issue with backup failing on AWS if using IAM profile without credentialsSecret by using credentialsSecret only when explicitly specified and relying on IAM roles instead (Thank you Itiel Olenick for reporting this issue)

- [K8SPXC-1541](https://perconadev.atlassian.net/browse/K8SPXC-1541) - Fixed Telemetry module to to consider both empty string "" and comma separated namespaces in cluster-wide mode

- [K8SPXC-1548](https://perconadev.atlassian.net/browse/K8SPXC-1548) Fixed the issue with deleting old backups on Google Cloud Storage by url-decoding the object path before deleting it (Thank you Mateusz Gruszkiewicz for reporting this issue)

- [K8SPXC-1631](https://perconadev.atlassian.net/browse/K8SPXC-1631) - Fixed the issue with the Operator restarting pod-0 after the cluster is ready. The issue is caused by ConfigMap and StatefulSet being created too close to each other and Kubernetes API can't return the newly created ConfigMap before creating the StatefulSet. The issue is fixed by reconciling the StatefulSet after the reconciliation of ConfigMap is completed.

- [K8SPXC-1664](https://perconadev.atlassian.net/browse/K8SPXC-1664) - Fixed the use of the proper script to check PXC nodes when adding them by HAProxy

##### Supported Software

The Operator was developed and tested with the following software:

- Percona XtraDB Cluster versions 8.4.5-5.1 (Tech preview), 8.0.42-33.1, and 5.7.44-31.65
- Percona XtraBackup versions 8.4.0-3, 8.0.35-34.1, and 2.4.29
- HAProxy 2.8.15-1
- ProxySQL 2.7.3
- LogCollector based on fluent-bit 4.0.1
- PMM Client 2.44.1 and 3.3.1

Other options may also work but have not been tested.

##### Supported Platforms

Percona Operators are designed for compatibility with all [CNCF-certified](https://www.cncf.io/training/certification/software-conformance/) Kubernetes distributions. Our release process includes targeted testing and validation on major cloud provider platforms and OpenShift, as detailed below for Operator version 1.16.0:

- [Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine) 1.30 - 1.33
- [Amazon Elastic Container Service for Kubernetes (EKS)](https://aws.amazon.com) 1.30 - 1.33
- [Azure Kubernetes Service (AKS)](https://azure.microsoft.com/en-us/services/kubernetes-service/) 1.30 - 1.33
- [OpenShift](https://www.redhat.com/en/technologies/cloud-computing/openshift) 4.15 - 4.19
- [Minikube](https://minikube.sigs.k8s.io/docs/) 1.36.0 based on Kubernetes 1.33.1

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.

### [`v1.17.0`](https://redirect.github.com/percona/percona-xtradb-cluster-operator/releases/tag/v1.17.0)

[Compare Source](https://redirect.github.com/percona/percona-xtradb-cluster-operator/compare/v1.16.1...v1.17.0)

#### Release Highlights

##### Improved observability for HAProxy and ProxySQL

Get insights into the HAProxy and ProxySQL performance by connecting to their statistics pages. Use the `cluster-name-haproxy:8084` and `cluster-name-proxysql:6070` endpoints to do so. Learn about other available ports in the [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/haproxy-conf.html).

##### Improved cluster load management during backups

If parallel backups overload your cluster, you can turn off parallel execution to prevent this. Previously, this meant that you could only run one backup at a time - no new backups could start until the current one was finished. Now, the Operator queues backups and runs them one after another automatically. You can fine-tune the backup sequence by setting the start time for all backups or for a specific on-demand one using the [`spec.backup.startingDeadlineSeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#backupstartingdeadlineseconds) Custom Resource option. This provides greater control over backup operations.

Another improvement is for the case when your database cluster becomes unhealthy, for example, when a Pod crashes or restarts. The Operator suspends running backups to reduce the cluster's load. Once the cluster recovers and reports a Ready status, the Operator resumes the suspended backup. To further offload the cluster during an unhealthy state, you can configure how long a backup remains suspended by using the [`spec.backup.suspendedDeadlineSeconds`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#backupsuspendeddeadlineseconds) Custom Resource option. If this time expires before the cluster recovers, the backup is marked as "failed."

##### Monitor PMM Client health and status

Percona Monitoring and Management (PMM) is a great tool to [monitor the health of your database cluster](https://docs.percona.com/percona-operator-for-mysql/pxc/monitoring.html). Now you can also learn if PMM itself is healthy using probes - a Kubernetes diagnostics mechanism to check the health and status of containers. Use the [`spec.pmm.readinessProbes.*`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pmmreadinessprobesinitialdelayseconds) and [`spec.pmm.livenessProbes.*`](https://docs.percona.com/percona-operator-for-mysql/pxc/operator.html#pmmlivenessprobesinitialdelayseconds) Custom Resource options to fine-tune Readiness and Liveness probes for PMM Client.

##### Improved observability of binary log backups

Get insights into the success and failure rates of binlog operations, timeliness of processing and uploads and potential gaps or inconsistencies in binlog data with the Prometheus metrics added for the Operator. Gather this data by connecting to the `<pitr-pod-service>:8080/metrics` endpoint. Learn more about the available metrics in the [documentation](https://docs.percona.com/percona-operator-for-mysql/pxc/backups-pitr.html#binary-logs-statistics).

#### Deprecation, Rename and Removal

The `spec.haproxy.exposePrimary.enabled` field is deprecated. If enabled via the `spec.haproxy.enabled`, the HAProxy primary service is already exposed.

#### New Features

- [K8SPXC-747](https://perconadev.atlassian.net/browse/K8SPXC-747), [K8SPXC-1473](https://perconadev.atlassian.net/browse/K8SPXC-1473) - Add the ability to access the statistics pages for HAProxy and ProxySQL

- [K8SPXC-1366](https://perconadev.atlassian.net/browse/K8SPXC-1366) - Add the ability to queue backups and run them sequentially, and to optimize the cluster load with the ability to suspend backups for an unhealthy cluster. A user can assign the start time and suspension time to backups to manage them better.

- [K8SPXC-1432](https://perconadev.atlassian.net/browse/K8SPXC-1432) - Enable users to configure cluster-wide Operator deployments in OpenShift certified catalog using OLM.

#### Improvements

- [K8SPXC-1367](https://perconadev.atlassian.net/browse/K8SPXC-1367) - Now a user can configure Readiness and Liveness probes for PMM Client container to check its health and status

- [K8SPXC-1461](https://perconadev.atlassian.net/browse/K8SPXC-1461) - Improve logging for resizing PVC with the information about successful and failed PVC resize. Log errors on resize attempts if the Storage Class doesn't support resizing.

- [K8SPXC-1466](https://perconadev.atlassian.net/browse/K8SPXC-1466) - Mark the containers that provide the service as default ones with the annotation. This enables a user to connect to a Pod without explicitly specifying a container.

- [K8SPXC-1473](https://perconadev.atlassian.net/browse/K8SPXC-1473) - Add the ability to connect to the built-in statistics pages for HAProxy and ProxySQL by exposing the ports for those pages

- [K8SPXC-1475](https://perconadev.atlassian.net/browse/K8SPXC-1475) - Update the backup image to use AWS CLI instead of MinIO CLI due to the license change

- [K8SPXC-1510](https://perconadev.atlassian.net/browse/K8SPXC-1510) - Add the ability to suppress messages about the use of deprecated features in MySQL Error Log by adding the `log_error_suppression_list` key from the `my.cnf` configuration file and defining the message number in the `spec.pxc.configuration` subsection of the Custom Resource manifest. See [how to change MySQL options](https://docs.percona.com/percona-operator-for-mysql/pxc/options.html) for steps. This improves readability for MySQL error log.

- [K8SPXC-1512](https://perconadev.atlassian.net/browse/K8SPXC-1512) - For Percona XtraDB Cluster version 8.4 and above, binary log user defined functions for point-in-time recovery (`binlog_utils_udf`) are now installed as a component instead of a plugin. This improves their compatibility across platforms and provides automatic dependency handling.

- [K8SPXC-1542](https://perconadev.atlassian.net/browse/K8SPXC-1542) - Improve binlog upload for large files to Azure blob storage with the ability to define the block size and the number of concurrent writers for the upload (Thanks to user dcaputo-harmoni for contribution)

- [K8SPXC-1543](https://perconadev.atlassian.net/browse/K8SPXC-1543) - Set PITR controller reference for binlog-collector deployment the same way as it's set for PXC and proxy StatefulSets. This creates a connection between PITR deployment and cluster resource (Thank you Vlad Gusev for the contribution)

- [K8SPXC-1544](https://perconadev.atlassian.net/browse/K8SPXC-1544) - Improve observability of binlog collector by adding the support of basic Prometheus metrics (Thank you Vlad Gusev for the contribution)

- [K8SPXC-1567](https://perconadev.atlassian.net/browse/K8SPXC-1567) - N

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://redirect.github.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/vexxhost/atmosphere).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4yNjQuMCIsInVwZGF0ZWRJblZlciI6IjQyLjg1LjEiLCJ0YXJnZXRCcmFuY2giOiJzdGFibGUvMjAyMy4xIiwibGFiZWxzIjpbInNraXAtcmVsZWFzZS1ub3RlcyJdfQ==-->

      patchset: 5d635ae7d201989f087661c6356a3703e1026788
      pipeline: check
      playbook_context:
        playbook_projects:
          trusted/project_0/vexxhost.dev/zuul-config:
            canonical_name: vexxhost.dev/zuul-config
            checkout: main
            commit: 9052b5a7781b3346e4cffd452a54448cbff54d8b
          trusted/project_1/opendev.org/zuul/zuul-jobs:
            canonical_name: opendev.org/zuul/zuul-jobs
            checkout: master
            commit: 691c03cc007bee9934da14cf46c86009616a2aef
          trusted/project_2/github.com/vexxhost/zuul-jobs:
            canonical_name: github.com/vexxhost/zuul-jobs
            checkout: main
            commit: a6e68243e02ef030ce5e75f8b67630880c475f33
          untrusted/project_0/github.com/vexxhost/zuul-jobs:
            canonical_name: github.com/vexxhost/zuul-jobs
            checkout: main
            commit: a6e68243e02ef030ce5e75f8b67630880c475f33
          untrusted/project_1/vexxhost.dev/zuul-config:
            canonical_name: vexxhost.dev/zuul-config
            checkout: main
            commit: 9052b5a7781b3346e4cffd452a54448cbff54d8b
          untrusted/project_2/opendev.org/zuul/zuul-jobs:
            canonical_name: opendev.org/zuul/zuul-jobs
            checkout: master
            commit: 691c03cc007bee9934da14cf46c86009616a2aef
          untrusted/project_3/github.com/vexxhost/atmosphere:
            canonical_name: github.com/vexxhost/atmosphere
            checkout: stable/2023.1
            commit: 5d635ae7d201989f087661c6356a3703e1026788
          untrusted/project_4/opendev.org/openstack/openstack-helm:
            canonical_name: opendev.org/openstack/openstack-helm
            checkout: master
            commit: aed8f582614604caa8594f2652804ec45990f1c0
        playbooks:
        - path: untrusted/project_0/github.com/vexxhost/zuul-jobs/playbooks/molecule/run.yaml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/playbook_0/role_1/zuul-jobs
            link_target: untrusted/project_2/opendev.org/zuul/zuul-jobs
            role_path: ansible/playbook_0/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: playbook branch
            link_name: ansible/playbook_0/role_2/zuul-jobs
            link_target: untrusted/project_0/github.com/vexxhost/zuul-jobs
            role_path: ansible/playbook_0/role_2/zuul-jobs/roles
      post_review: false
      post_timeout: null
      pre_timeout: null
      project:
        canonical_hostname: github.com
        canonical_name: github.com/vexxhost/atmosphere
        name: vexxhost/atmosphere
        short_name: atmosphere
        src_dir: src/github.com/vexxhost/atmosphere
      projects:
        github.com/vexxhost/atmosphere:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/atmosphere
          checkout: stable/2023.1
          checkout_description: zuul branch
          commit: 5d635ae7d201989f087661c6356a3703e1026788
          name: vexxhost/atmosphere
          required: false
          short_name: atmosphere
          src_dir: src/github.com/vexxhost/atmosphere
      ref: refs/pull/2595/head
      resources: {}
      tenant: oss
      timeout: 1800
      topic: null
      voting: true
