You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0ffc5bf
Browse filesBrowse the repository at this point in the historyBrowse files
fix(pooler): clear stale TLS status fields when configuration is removed (#9397)
The pooler status update logic only set status fields when resources
were present, but never cleared them when absent. This caused stale TLS
configuration (ServerCA, ClientCA, ClientTLS, ServerTLS) to persist in
status even after being removed from the spec, breaking pooler
connectivity.
This particularly impacts users upgrading to v1.28 from any prior
version.
Before v1.28, the ServerTLS status field was always set to the cluster's
server certificate. In v1.28, this field was repurposed for optional
manual
TLS authentication to PostgreSQL. On upgrade, the stale pre-v1.28 value
persists, causing pgbouncer to use the wrong certificate and fail with
"ssl/tls alert unsupported certificate" errors. This breaks all
application
connectivity through the pooler.
The same issue affects any user who configures custom TLS settings and
later removes them - pgbouncer continues using the stale certificates until
manually intervened.
This fix adds explicit clearing of optional TLS status fields when the
corresponding resources are not configured, ensuring status accurately
reflects
the current specification.
Closes#9392
Signed-off-by: Marco Nenciarini <[email protected]>
Signed-off-by: Armando Ruocco <[email protected]>
Co-authored-by: Armando Ruocco <[email protected]>
0 commit comments