1.240 archivos perdidos y un checkout caído 35 minutos: el caso real que explica networking y storage en Kubernetes, y cómo evitarlo.

We're excited to announce the alpha support for a changed block tracking mechanism. This enhances the Kubernetes storage ecosystem by providing an efficient way for CSI storage drivers to identify changed blocks in PersistentVolume snapshots. With a driver that can use the feature, you could benefit from faster and more resource-efficient backup operations. If you're eager to try this feature, you can skip to the Getting Started section. What is changed block tracking?

I am thrilled to announce that the feature to prevent PersistentVolume (or PVs for short) leaks when deleting out of order has graduated to General Availability (GA) in Kubernetes v1.33! This improvement, initially introduced as a beta feature in Kubernetes v1.31, ensures that your storage resources are properly reclaimed, preventing unwanted leaks. How did reclaim work in previous Kubernetes releases? PersistentVolumeClaim (or PVC for short) is a user's request for storage.

PersistentVolume (or PVs for short) are associated with Reclaim Policy. The reclaim policy is used to determine the actions that need to be taken by the storage backend on deletion of the PVC Bound to a PV. When the reclaim policy is Delete, the expectation is that the storage backend releases the storage resource allocated for the PV. In essence, the reclaim policy needs to be honored on PV deletion.

Announcing the graduation to General Availability (GA) of the PersistentVolume lastTransitionTime status field, in Kubernetes v1.31! The Kubernetes SIG Storage team is excited to announce that the "PersistentVolumeLastPhaseTransitionTime" feature, introduced as an alpha in Kubernetes v1.28, has now reached GA status and is officially part of the Kubernetes v1.31 release. This enhancement helps Kubernetes users understand when a PersistentVolume transitions between different phases, allowing for more efficient and informed resource management.

The PersistentVolume node affinity API dates back to Kubernetes v1.10. It is widely used to express that volumes may not be equally accessible by all nodes in the cluster. This field was previously immutable,...

I am thrilled to announce that the feature to prevent PersistentVolume (or PVs for short) leaks when deleting out of order has graduated to General Availability (GA) in Kubernetes v1.33! This improvement,...

**Bulletin ID:** 2026-016-AWS **Scope:** AWS **Content Type:** Important (requires attention) **Publication Date:** 2026/04/17 11:15 AM PDT **Description:** The Amazon EFS CSI Driver is a Container Storage Interface driver that allows Kubernetes clusters to use Amazon Elastic File System. We identified CVE-2026-6437, where an actor with PersistentVolume creation privileges can inject arbitrary mount options via two unsanitized fields: the Access Point ID in volumeHandle and the mounttargetip volumeAttribute. In both cases, appending comma-separated values causes the mount utility to parse them as separate mount options. No AWS service is affected. **Impacted versions:** EFS CSI Driver <&equal; v3.0.0 **Please refer to the article below for the most up-to-date and complete information related to this AWS Security Bulletin.**

Posted by Vinayak Goyal on Apr 10 Hello Kubernetes Community, A vulnerability was identified in the Kubernetes CSI Driver for SMB where insufficient validation of the subDir parameter in volume identifiers could allow path traversal. A malicious user with the ability to create a PersistentVolume referencing the SMB CSI driver could craft a volumeHandle containing traversal sequences (for example ../). When the driver performs cleanup operations during volume deletion, these...

Borraste el Deployment pero los datos siguen en disco. Así re-vinculás el volumen Retain y levantás el pod sin perder nada.

¿Los Deployments borran tus datos en Kubernetes? Spoiler: no. El experimento de 10 minutos que aclara cuándo usar cada uno.

Production-Grade Container Scheduling and Management - kubernetes/kubernetes

VeleroはKubernetesクラスターのディザスタリカバリデータ移行データ保護を提供できる人気のオープンソースツールですVeleroはKubernetesクラスターリソースと永続ボリュームPersistentVolumeをオンデマンドまたはスケジュールに従ってサポートされた外部のストレージバックエンドにバックアップできますこのブログ記事ではVeleroを使用してAmazonEKSクラスターのリソースをバックアップリストア移行する方法に焦点を当て組織のユースケースに最適なアプローチを決定するためにVeleroが提供するバックアップオプションを紹介します

Du willst ein PersistentVolume (PV) in Kubernetes vergrößern? In diesem Blogeintrag erfährst du wie das funktioniert.