CloudNativePG
v1.27.4Storage & Data2026년 4월 1일
유지보수 릴리스로, 정확성 문제와 보안 정보 노출을 고치고 공급망 관련 개선과 동작 및 호환성 변경을 담았습니다. 지원이 끝난 `1.27` 계열을 사용 중이라면 더 새로운 마이너 버전으로의 이전을 계획해야 합니다.
영향 확인 (2)
security조정 중 역할 암호 로그 노출 방지
PostgreSQL이 특정 조정 단계에 있을 때 적용됩니다.특정 조정 단계에서
PostgreSQL이 역할 암호를 로그에 노출할 수 있던 보안 문제를 수정했습니다.breaking
1.계열의 마지막 릴리스27. x 지원되지 않는
1.계열을 사용하는 경우에 적용됩니다.27 1.계열의 마지막 릴리스이며,27. x 1.은 더 이상 지원되지 않습니다. 더 새로운 마이너 버전으로 업그레이드할 것이 권장됩니다.27
미리 준비 (1)
deprecated
native (in-tree) Barman Cloud support제거 시점 변경1.30.0에서 제거 예정native (in-tree) Barman Cloud support를 사용하는 경우에 적용됩니다.native (in-tree) Barman Cloud support의 지원 중단 안내가 갱신되어 제거 시점이1.에서29. 0 1.으로 변경되었습니다.30. 0 Barman Cloud Plugin으로 이전할 것이 계속 권장됩니다.
그 외 기록된 변경 21건 전체fixes 12 · value changes 5 · constraints 2 · additions 1 · defaults 1
fixes (12)
- - Fixed an issue where fencing annotations could not be processed when the WAL disk was full, because the disk space check blocked the instance manager from starting. The check is now performed later in the lifecycle loop, after fencing is evaluated. ([\#10302](https://github.com/cloudnative-pg/cloudnative-pg/pull/10302)) <!-- 1.28 1.27 -->
- - Fixed an issue where replicas would get stuck in a
Pendingstate if theVolumeSnapshotused for the initial bootstrap had been deleted. The operator now validates snapshot existence before use; if a snapshot is missing, it attempts to use the next available candidate or falls back topg_basebackup. ([\#10192](https://github.com/cloudnative-pg/cloudnative-pg/pull/10192)) <!-- 1.28 1.27 1.25 --> - - Prevented the "supervised primary" rollout strategy from consuming all available rollout slots, which previously caused delays in scheduled updates. Contributed by @ermakov-oleg. ([\#9977](https://github.com/cloudnative-pg/cloudnative-pg/pull/9977)) <!-- 1.28 1.27 1.25 -->
- - Fixed an issue where certain hot-standby parameter changes were not being correctly applied to replica clusters. ([\#9952](https://github.com/cloudnative-pg/cloudnative-pg/pull/9952)) <!-- 1.28 1.27 1.25 -->
- - Fixed a bug in the CNPG-I reconciler hook that could lead to skipping subsequent plugins when a "continue" result was returned. Contributed by @sharifmshaker. ([\#9978](https://github.com/cloudnative-pg/cloudnative-pg/pull/9978)) <!-- 1.28 1.27 -->
- - Fixed a deadlock scenario that occurred when attempting to resize a filesystem on a PVC that was not currently attached to a Pod. Contributed by @jmealo. ([\#9981](https://github.com/cloudnative-pg/cloudnative-pg/pull/9981)) <!-- 1.28 1.27 -->
- - Fixed webhook validation of bootstrap recovery sources to accept external clusters configured with
ConnectionParameters(forpg_basebackup-based recovery). Previously, these were incorrectly rejected unless a Barman object store or CNPG-i plugin was also configured. ([\#10268](https://github.com/cloudnative-pg/cloudnative-pg/pull/10268)) <!-- 1.28 1.27 1.25 --> - - Fixed fencing to work correctly even when the target pod does not exist. Fencing operates on a cluster-level annotation and should not depend on pod existence; instance name validation is now performed only in the
cnpg fencing oncommand. ([\#10035](https://github.com/cloudnative-pg/cloudnative-pg/pull/10035)) <!-- 1.28 1.27 1.25 --> - - Fixed the cluster and pooler service reconcilers to correctly handle changes to all spec fields when using the patch update strategy. The reconciler now uses RFC 7386 JSON Merge Patching, preventing cloud-provider-set fields (such as
loadBalancerClass) from being inadvertently removed. ([\#10190](https://github.com/cloudnative-pg/cloudnative-pg/pull/10190), [\#10311](https://github.com/cloudnative-pg/cloudnative-pg/pull/10311)) <!-- 1.28 1.27 1.25 --> - - Fixed a race condition in the deprecated in-tree Barman Cloud backup implementation affecting parallel WAL restore, where prefetched files could be read while still being downloaded, causing PostgreSQL recovery to fail with "invalid checkpoint record" errors. ([\#10285](https://github.com/cloudnative-pg/cloudnative-pg/pull/10285)) <!-- 1.28 1.27 1.25 -->
- - Fixed the timeline history file validation to also apply to plugin-based WAL restore. Previously, the protection introduced in [\#9650](https://github.com/cloudnative-pg/cloudnative-pg/pull/9650) only covered in-tree restores, allowing plugins to bypass the check and download future timeline history files, causing timeline mismatch errors on replicas. ([\#9849](https://github.com/cloudnative-pg/cloudnative-pg/pull/9849)) <!-- 1.28 1.27 1.25 -->
- - The cnpg plugin now correctly propagates ImagePullSecrets to the
pgbenchJob pod template. ([\#10174](https://github.com/cloudnative-pg/cloudnative-pg/pull/10174)) <!-- 1.28 1.27 1.25 -->
value changes (5)
- - Improved role management by verifying the instance is the primary before each reconciliation cycle, avoiding unnecessary reconciliation attempts and spurious error messages on read-only replicas. ([\#9971](https://github.com/cloudnative-pg/cloudnative-pg/pull/9971)) <!-- 1.28 1.27 1.25 -->
- - The operator now honors the
primaryUpdateMethodwhen adding new PVCs to a cluster, ensuring that the rollout strategy (e.g., switchover vs. restart) is respected during storage expansion or additions. ([\#9720](https://github.com/cloudnative-pg/cloudnative-pg/pull/9720)) <!-- 1.28 1.27 --> - - Updated the default PostgreSQL version to 18.3 (image
18.). ([\#10090](https://github.com/cloudnative-pg/cloudnative-pg/pull/10090)) <!-- 1.28 1.27 1.25 -->3-system-trixie - - Volume names for extensions and tablespaces are now prefixed to avoid naming collisions with standard cluster volumes. ([\#9973](https://github.com/cloudnative-pg/cloudnative-pg/pull/9973)) <!-- 1.28 1.27 -->
- - When hibernating a non-healthy cluster, the operator now reports a
WaitingForHealthycondition, making the deferred hibernation state visible throughcnpg status. ([\#10193](https://github.com/cloudnative-pg/cloudnative-pg/pull/10193)) <!-- 1.28 1.27 1.25 -->
constraints (2)
- - Improved the
PoolerCRD with support for granular configuration of TLS cipher suites and minimum/maximum TLS versions. This enables administrators to meet strict security compliance requirements for pooler-to-client and pooler-to-server connections. Contributed by @alex1989hu. ([\#9571](https://github.com/cloudnative-pg/cloudnative-pg/pull/9571)) <!-- 1.28 1.27 1.25 --> - - Extended the CRD schemas for
Cluster,ImageCatalog, andClusterImageCatalogto accept theextensions,bin_path, andenvfields introduced in 1.29. The operator ignores these fields on older versions, but accepting them in the schema allows users to share a single manifest across clusters running different CNPG versions. ([\#10131](https://github.com/cloudnative-pg/cloudnative-pg/pull/10131), [\#10387](https://github.com/cloudnative-pg/cloudnative-pg/pull/10387)) <!-- 1.28 1.27 -->
additions (1)
- - **SLSA provenance and SBOMs**: added SLSA (Supply-chain Levels for Software Artifacts) provenance to release binaries and container images. Additionally, enabled Software Bill of Materials (SBOM) generation within the GoReleaser pipeline for improved dependency transparency. ([\#10048](https://github.com/cloudnative-pg/cloudnative-pg/pull/10048), <!-- 1.28 1.27 1.25 --> [\#10074](https://github.com/cloudnative-pg/cloudnative-pg/pull/10074)) <!-- 1.28 1.27 1.25 -->
defaults (1)
- - Improved the reliability of major upgrades by setting
BackoffLimit=0on the upgrade job, preventing unnecessary retries of a failedpg_upgrade. The operator now automatically deletes the failed job when a user reverts the container image, allowing the cluster to restart gracefully on the original version. ([\#10104](https://github.com/cloudnative-pg/cloudnative-pg/pull/10104), [\#10298](https://github.com/cloudnative-pg/cloudnative-pg/pull/10298)) <!-- 1.28 1.27 -->
CloudNativePG 스택에 추가
조치가 필요한 릴리스가 나왔을 때 주간 메일로 알려드립니다. 이번 릴리스의 보안 패치와 브레이킹 체인지 같은 것들입니다.