RATATOSKRATATOSK
로그인

CloudNativePG

v1.29.3Storage & Data
2026년 9월 23일

ACTION 2CHECK 1OTHER 38

장애 조치, 복구, 관측성, 정리 동작을 다듬은 유지 보수 릴리스이며, 보안 검증 오류와 취약한 의존성도 바로잡았습니다. `1.29` 계열 사용자는 지원되는 새 마이너 버전으로 업그레이드하는 것이 권장됩니다.

조치 필요 (2)

  • securityhighgoogle.golang.org/grpc 보안 업데이트

    google.golang.org/grpc를 v1.83.1로 업데이트했습니다. HTTP/2 DATA 프레임 조각화로 발생하는 gRPC-Go 힙 메모리 고갈 문제인 CVE-2026-84304 및 GHSA-vp52-pcj8-j9qc를 수정합니다.

    CVE-2026-84304

  • security웹훅 확장 경로 검증 수정

    웹훅이 절대 확장 경로에 포함된 .. 경로 이동을 원시 경로만 검사한 뒤 허용하던 문제를 수정했습니다. 예를 들어 /a/../../../../etc 같은 경로가 실행 시 확장 기능의 마운트 지점을 벗어나던 동작이 차단됩니다.

영향 확인 (1)

  • breaking1.29.x 계열 지원 종료

    1.29 계열을 사용하는 경우에 적용됩니다.

    이번 릴리스는 1.29.x 계열의 마지막 릴리스이며, 1.29는 더 이상 지원되지 않습니다. 지원되는 새 마이너 버전으로 업그레이드하는 것이 적극 권장됩니다.

그 외 기록된 변경 38건 전체fixes 29 · additions 3 · defaults 2 · value changes 2 · constraints 1 · renames 1

fixes (29)

  • Fixed PgBouncer metrics silently reporting zero when PgBouncer adds or reorders columns: SHOW STATS and SHOW POOLS results are now matched by column name instead of by position.
  • Demoted an unreachable old primary immediately during failover, instead of waiting on checkpoint and fast-shutdown attempts that could never complete.
  • Fixed failover and Pod recreation getting stuck while any instance in the cluster was fenced.
  • Fixed a failover that could stall forever or get silently reverted.
  • Fixed the designated-primary sort in PostgresqlStatusList so a tie on LSN no longer sorts it out of order.
  • Stopped abandoning a fast shutdown after 60 seconds.
  • Waited for certificate status before refreshing secrets during bootstrap.
  • Fixed in-tree Barman Cloud recovery ignoring wal.maxParallel and wal.restoreAdditionalCommandArgs, fetching WAL one segment at a time instead of using the configured parallelism.
  • Honored the unrecoverable annotation on pending and terminating instances.
  • Honored Backup.spec.online when finalizing VolumeSnapshot-based backups, so a cold backup is no longer reported as online in status.
  • Retried volume snapshot backups on transient instance-manager connection errors (e.g. a dial timeout from a brief pod-network disruption), instead of failing the backup outright.
  • Set --no-data-checksums explicitly when .spec.postgresql.dataChecksums is false on PostgreSQL 18+, which now enables checksums by default in initdb.
  • Stopped discarding .spec.inheritedMetadata labels on PVC reconciliation; they were applied before, and then overwritten by, the operator's own labels.
  • Stopped Pooler and DatabaseRole from recreating their owned resources after being marked for deletion, which could block an external finalizer (e.g. ArgoCD foreground deletion) waiting for those resources to disappear.
  • Handled a NULL stats_reset value in the pg_stat_wal metric, which could occasionally break Prometheus scraping on PostgreSQL 18 clusters.
  • Recovered log streaming when a stale non-FIFO file blocked the log pipe.
  • Stopped sampling logs of the Pods' processes, so no log lines are silently dropped.
  • Stopped caching Helm release Secrets in the operator, which could spike memory usage and crashloop the operator on clusters with large Helm releases installed alongside it.
  • Re-ran owned-resource finalizer cleanup after an operator restart, so a namespace deleted while the operator was down doesn't hang in Terminating forever.
  • Fixed rejoining replicas taking a long time to complete pg_rewind when WAL prefetching (wal.maxParallel > 1) was enabled.
  • Treated a PostgreSQL instance rejecting connections as started up in probes.
  • Stopped issuing a redundant PATCH on every reconciliation when a cluster's pvcTemplate set volumeAttributesClass.
  • Stopped halting replication slot reconciliation at the first failing slot.
  • During rollouts, compared the running configuration hash, rather than the on-disk one, avoiding unnecessary switchovers.
  • Retried VolumeSnapshot errors until the deadline, instead of giving up early.
  • Symlinked pg_wal to the WAL volume during plugin-based recovery, instead of replaying WAL onto the data volume, which could exhaust it on a large point-in-time recovery.
  • Reported the Postgres capabilities of a plugin correctly.
  • Prevented the plugin status field from flapping on Cluster reconciliation.
  • Deleted PVCs before Pods in cnpg destroy, avoiding a race that could leave dangling PVCs needing a second invocation to clean up.

additions (3)

  • Added restoreAdditionalCommandArgs to .barmanObjectStore.data for in-tree Barman Cloud recoveries, so custom flags are forwarded to barman-cloud-restore during recovery.
  • Added support for setting auth_user in spec.pgbouncer.parameters to override the user PgBouncer uses for its auth_query connection, instead of always deriving it from the authQuerySecret.
  • Added a --dry-run option to the backup command that prints the Backup resource that would be created, without creating it.

defaults (2)

  • Updated the default PostgreSQL operand image to 18.6-system-trixie.
  • Used UTC time zone for the default backup name.

value changes (2)

  • the operator now computes the check_empty_wal_archive decision once and passes it to CNPG-I plugins on both WAL archiving and restore hooks.
  • Moved the operator's own base image from Debian 12 (bookworm) to Debian 13 (trixie), now that Debian 12 has moved to LTS-only maintenance.

constraints (1)

  • Allowed setting the ssl_ecdh_curve PostgreSQL parameter in .spec.postgresql.parameters. It was previously rejected by the validating webhook even though the operator does not manage it.

renames (1)

  • Replaced a finalizer with in-memory cleanup on Service deletion.
CloudNativePG 스택에 추가

조치가 필요한 릴리스가 나왔을 때 주간 메일로 알려드립니다. 이번 릴리스의 보안 패치와 브레이킹 체인지 같은 것들입니다.

스택에 추가 →
공식 릴리스 노트 ↗CloudNativePG 릴리스 전체 →