CloudNativePG
v1.27.3Storage & Data2026년 2월 5일
유지보수 성격의 릴리스로, Azure 인증 방식 추가와 정확성, 검증, 성능 개선이 포함되어 있습니다. 공개된 보안 변경은 없습니다.
영향 확인 (1)
breakingAzure 오브젝트 저장소 인증 설정 검증 강화
Azure 오브젝트 저장소 설정에서 저장소 키나 SAS 토큰 같은 명시적 자격 증명을 사용하는 경우에 적용됩니다.
Azure 오브젝트 저장소에서 명시적 자격 증명을 사용할 때
storageAccount를 반드시 지정하도록 검증합니다.connectionString은 다른 인증 매개변수와 함께 사용할 수 없습니다.
그 외 기록된 변경 18건 전체fixes 13 · value changes 4 · additions 1
fixes (13)
- - Fixed validation of PostgreSQL extension names containing underscores (e.g.,
pg_partman,pg_ivm). Extension names with underscores are automatically sanitized to use hyphens for Kubernetes volume names while preserving the original name in mount paths. Webhook validation prevents naming conflicts after sanitization. Contributed by @shusaan. ([\#9386](https://github.com/cloudnative-pg/cloudnative-pg/pull/9386)) <!-- 1.27 --> - - Fixed a critical issue where the
TimelineIDin the cluster status was not reset to 1 after a major version upgrade. Becausepg_upgradeinitializes a new timeline, keeping the old ID (e.g., timeline 2) caused replicas to attempt to restore incompatible history files from object storage, leading to fatal "requested timeline is not a child of this server's history" errors. ([\#9830](https://github.com/cloudnative-pg/cloudnative-pg/pull/9830)) <!-- 1.27 --> - - Fixed a bug where replicas could enter a crash-loop by attempting to download timeline history files from future timelines. This occurred when stale files remained in the WAL archive from a previous cluster life, and replicas would incorrectly try to fetch them during recovery. ([\#9650](https://github.com/cloudnative-pg/cloudnative-pg/pull/9650)) <!-- 1.27 1.25 -->
- - Fixed a race condition in
replica_clustersetups during designated primary transitions, preventing transient "no primary" states in the replica cluster. ([\#9601](https://github.com/cloudnative-pg/cloudnative-pg/pull/9601)) <!-- 1.27 1.25 --> - - The backup controller now uses the unique instance session ID to detect instance manager restarts. This prevents the operator from incorrectly assuming a backup is still progressing if the underlying container has crashed and restarted, which previously led to orphaned backup objects. ([\#9370](https://github.com/cloudnative-pg/cloudnative-pg/pull/9370)) <!-- 1.27 -->
- - Fixed an issue where replication slots were not properly dropped from replicas when the feature was disabled or the cluster was reconfigured. This ensures that unused slots do not cause WAL build-up on the primary. ([\#9381](https://github.com/cloudnative-pg/cloudnative-pg/pull/9381)) <!-- 1.27 1.25 -->
- - Fixed an issue where
imagePullSecretswere not added to theServiceAccountcreated for thePooler. Previously, these secrets were applied to the Deployment but not the SA, which caused image pull failures in restricted environments using certain security policies. ([\#9427](https://github.com/cloudnative-pg/cloudnative-pg/pull/9427)) <!-- 1.27 1.25 --> - - Added a check to verify ownership before the operator deletes a
PodMonitor. This prevents the operator from accidentally deleting manually managed monitoring resources that happen to share a name with expected CNPG resources. Contributed by @juliamertz. ([\#9340](https://github.com/cloudnative-pg/cloudnative-pg/pull/9340)) <!-- 1.27 1.25 --> - - Fixed a bug where
pg_stat_archivermetrics would continue to report stale data on standby instances after a switchover. The exporter now skips these metrics on standbys, as PostgreSQL only provides valid archiver stats on the primary. ([\#9411](https://github.com/cloudnative-pg/cloudnative-pg/pull/9411)) <!-- 1.27 1.25 --> - - Fixed backup status updates to prevent "resource has been modified" errors during concurrent updates. ([\#9551](https://github.com/cloudnative-pg/cloudnative-pg/pull/9551)) <!-- 1.27 1.25 -->
- - Fixed event reporting to use the correct pod name when a backup pod is not found. ([\#9552](https://github.com/cloudnative-pg/cloudnative-pg/pull/9552)) <!-- 1.27 1.25 -->
- - Fixed error handling when removing finalizers on
Databaseobjects. ([\#9431](https://github.com/cloudnative-pg/cloudnative-pg/pull/9431)) <!-- 1.27 1.25 --> - - Fixed the
logs --followcommand to continue polling for new pods instead of exiting prematurely when all current log streams complete. ([\#9599](https://github.com/cloudnative-pg/cloudnative-pg/pull/9599)) <!-- 1.27 1.25 -->
value changes (4)
- - Optimized the deletion path so the operator begins cleaning up resources immediately when a cluster is marked for deletion. This significantly reduces the time a cluster remains in
Terminatingstatus while waiting for internal reconciliation loops. ([\#9555](https://github.com/cloudnative-pg/cloudnative-pg/pull/9555)) <!-- 1.27 1.25 --> - - Clarified the interpretation of timestamp formats for recovery
targetTime. Timestamps provided without an explicit timezone are now consistently interpreted as UTC. Contributed by @pchovelon. ([\#8937](https://github.com/cloudnative-pg/cloudnative-pg/pull/8937)) <!-- 1.27 1.25 --> - - Improved performance of scheduled backup operations for clusters with a very high number of historical backups. ([\#9489](https://github.com/cloudnative-pg/cloudnative-pg/pull/9489)) <!-- 1.27 1.25 -->
- - Updated the
statuscommand to display "Disabled" when theskipWalArchivingannotation is present on a cluster. This replaces confusing "starting up" or "unknown" states when WAL archiving is intentionally bypassed. ([\#9709](https://github.com/cloudnative-pg/cloudnative-pg/pull/9709)) <!-- 1.27 1.25 -->
additions (1)
- - Added support for Azure's
DefaultAzureCredentialauthentication mechanism for backup and recovery operations. This can be enabled by settingazureCredentials.in the backup configuration, simplifying authentication in Azure environments without requiring explicit storage account keys or SAS tokens. ([\#9468](https://github.com/cloudnative-pg/cloudnative-pg/pull/9468)) <!-- 1.27 1.25 -->useDefaultAzureCredentials: true
CloudNativePG 스택에 추가
조치가 필요한 릴리스가 나왔을 때 주간 메일로 알려드립니다. 이번 릴리스의 브레이킹 체인지 같은 것들입니다.