Issues
- Sidecars for pgbouncer do not workK8SPG-645Resolved issue: K8SPG-645Julio Pasinatto
- Tolerations not rendered correctly in pg-db helm chartK8SPG-644Resolved issue: K8SPG-644Julio Pasinatto
- PG Cluster is in initializing status after restroing to a different K8s environmentK8SPG-622Resolved issue: K8SPG-622
- Need a feature for introducing custom delay on the entrypoint of the backup podK8SPG-615ege.gunes
- Multiple Percona Postgresql Operator pods for the same deployment could process custom resource changes in parallelK8SPG-614Resolved issue: K8SPG-614Julio Pasinatto
- duplicate entries when add env by initContainersK8SPG-608Aaditya Dubey
- CPU resources with a decimal is failingK8SPG-599Aaditya Dubey
- Run DROP EXTENSION on extension deletionK8SPG-594Resolved issue: K8SPG-594dmitriy.kostiuk
- Vulnerabilities have been reported in the images we shipped.K8SPG-591
- Failed restore puts the cluster in a broken stateK8SPG-587Resolved issue: K8SPG-587Eleonora Zinchenko
- Helm - add namespace reference to templatesK8SPG-585Resolved issue: K8SPG-585Tomislav Plavcic
- Documentation is wrong in how to define which backup to restore fromK8SPG-581Resolved issue: K8SPG-581Eleonora Zinchenko
- Unable to tell which exact version an image providesK8SPG-580Resolved issue: K8SPG-580dmitriy.kostiuk
- PostgreSQL major upgrade process is brokenK8SPG-579Resolved issue: K8SPG-579
- Support workload identity on GKE in PGK8SPG-578natalia.marukovich
- PMM query source for PostgreSQL is hard-coded to pgstatmonitorK8SPG-577Resolved issue: K8SPG-577dmitriy.kostiuk
- Documentation is misleading in terms of enabling built-in extensionsK8SPG-575Resolved issue: K8SPG-575dmitriy.kostiuk
- pg_repack is not included despite being listed as a builtin extensionK8SPG-574Eleonora Zinchenko
- helm - add possibility to specify storage class nameK8SPG-573dmitriy.kostiuk
- helm - indentation issue with pgbouncer configK8SPG-572Resolved issue: K8SPG-572Tomislav Plavcic
- When we create a user with the cr.yaml and define a database, assign it to the userK8SPG-571natalia.marukovich
- It's not feasible to pre-define a new user passwordK8SPG-570
- helm pg-db: Fix exposing of pgBouncer load balancingK8SPG-564Resolved issue: K8SPG-564Pavel Tankov
- pg-db helm chart - Fix multiple labels for topologySpreadConstraintsK8SPG-563Resolved issue: K8SPG-563Tomislav Plavcic
- docs/helm - support for incremental backupsK8SPG-562dmitriy.kostiuk
- pg-db helm chart - fix restoring backup without clusterK8SPG-546Resolved issue: K8SPG-546Tomislav Plavcic
- pg-db - fix differential backup schedule and allow any repo combinationK8SPG-541Resolved issue: K8SPG-541Tomislav Plavcic
- Steps for setting up Streaming replication for DR cluster.K8SPG-539Resolved issue: K8SPG-539dmitriy.kostiuk
- When we try to run backup with non-existent repo operator crashes.K8SPG-535Resolved issue: K8SPG-535Pavel Tankov
- use_slots defaults at falseK8SPG-534Resolved issue: K8SPG-534Pavel Tankov
- Handle replication slots in helm templatesK8SPG-533Resolved issue: K8SPG-533Julio Pasinatto
- wrong log level message when data source doesn't existK8SPG-532natalia.marukovich
- pg-db helm chart - lint issues and un-wrapped template valuesK8SPG-529Resolved issue: K8SPG-529Tomislav Plavcic
- pg-db helm - allow passing asterisk at the beginning of a backup scheduleK8SPG-528Resolved issue: K8SPG-528Tomislav Plavcic
- installing the pg-db cluster using helm, instance was not able to allocation resourcesK8SPG-527Resolved issue: K8SPG-527Tomislav Plavcic
- pg-db helm chart - fix for pgbackrest global section fails to renderK8SPG-524Resolved issue: K8SPG-524Tomislav Plavcic
- Cluster is broken if PG_VERSION file is missing during upgrade from 2.2.0 to 2.3.1K8SPG-522Resolved issue: K8SPG-522Pavel Tankov
- upgrade path described in the documentation leads to built-in extensions disabledK8SPG-521Resolved issue: K8SPG-521dmitriy.kostiuk
- pgbackrest zst/lz4 compressionK8SPG-516Resolved issue: K8SPG-516Slava Sarzhan
- It is not possible to connect through pgbouncer with a new database userK8SPG-515Resolved issue: K8SPG-515
- Cluster state set to paused while pods are still runningK8SPG-510Resolved issue: K8SPG-510Pavel Tankov
- We had a case where restore status was showing true without any restore running.K8SPG-509Resolved issue: K8SPG-509Andrii Dema
- Backup jobs not being cleaned up since 2.3.1K8SPG-502Resolved issue: K8SPG-502Pavel Tankov
- cluster stuck in init state if pgbackrest secret doesn't existK8SPG-499Resolved issue: K8SPG-499Eleonora Zinchenko
- Release 2.3.1K8SPG-497Resolved issue: K8SPG-497Tomislav Plavcic
- Build a docker image for every minor version of Percona PostgresqlK8SPG-261
46 of 46
Sidecars for pgbouncer do not work
Done
General
Escalation
General
Escalation
Description
Environment
None
Created October 1, 2024 at 7:02 AM
Updated March 17, 2025 at 5:49 PM
Resolved February 4, 2025 at 5:01 PM
Activity
Julio PasinattoFebruary 4, 2025 at 5:00 PM
Verified.
with:
The securityContext will be done in
Slava SarzhanDecember 11, 2024 at 6:08 PM
The issue was fixed.
Follow up on:
Operator Version: 2.3.1, 2.4.0, 2.4.1
Summary: I want to add sidecars to pgbouncer Pods through a section in CR. Even they are in CR, they do not appear in the Pod. There are no errors in the Operator log.
Steps to reproduce:
Take default cr.yaml
Add sidecars section into
spec.proxy.pgBouncerResult: no sidecar container created
Expectations: sidecar is added