allows any existing storage driver that supports dynamic provisioning to be used as an ephemeral volume with the volume’s lifecycle bound to the Pod. It can be used to provide scratch storage that is different from the root disk, for example persistent memory, or a separate local disk on that node. All StorageClass parameters for volume provisioning are supported. All features supported with PersistentVolumeClaims are supported, such as storage capacity tracking, snapshots and restore, and volume resizing....

disk2/testbucket/file/9f6c3be2-463f-4771-a6c7-1204baaa3ff2/part.1 disk2/testbucket/file/xl.meta XL2 Æ X ¨Versions‘‚¤Type ¥V2ObjÞ ¢IDÄ ¤DDirÄ Ÿl;âF?Gq¦Ç ºª?ò¦EcAlgo £EcM £EcN §EcBSizeÒ §EcIndex ¦EcDist” ¨CSumAlgo ¨PartNums‘ ©PartETags‘ ©PartSizes‘Ò ªPartASizes‘Ò ¤SizeÒ ¥MTimeÓ ð ÞÍ &˜§MetaSys ¼x-minio-internal-inline-dataÄ true§MetaUsr‚¤etagÙ fffb6377948ebea75ad2¬content-type¸application/octet-streamÎ7£ï; disk1/testbucket/file/xl.meta 䱘′ ÆĀ腘嚨牥楳湯酳ꒂ祔数ꔁ㉖扏 ᄀ䦢쑄 ꐀ䑄物Ⴤ沟㽆煇잦Вꪺ䖦䅣杬ů䖣䵣ꌂ捅Ɏ䖧䉣楓敺Ò ꜀捅湉敤ɸ䖦䑣獩鑴̂...

 - Newly provisioned PVs by Azure disk will no longer have the beta `FailureDomain` label. Azure disk volume plugin will start to have GA topology label instead. ([#101534](https://github.com/kubernetes/kubernetes/pull/101534), [@kassarl](https://github.com/kassarl))

Volumes (SMB 2.1 and 3.0) into a Pod. See [example](https://github.com/kubernetes/kubernetes/blob/release-1.2/examples/azure_file/README.md) for details.
  * Logs usage and root filesystem usage of a container, volumes usage of a pod and node disk usage are exposed through Kubelet new metrics API.

### Experimental Features

  * Dynamic Provisioning of PersistentVolumes: Kubernetes previously required all

		// https://en.wikipedia.org/wiki/Copy_protection so the incoming stream
		// is always going to be in-memory as we cannot re-read from what we
		// wrote to disk - since that amounts to "copying" from a "copy"
		// instead of "copying" from source, we need the stream to be seekable
		// to ensure that we can make fan-out calls concurrently.
		buf := bytebufferpool.Get()

### Bug or Regression

- Fix: delete non existing Azure disk issue ([#107406](https://github.com/kubernetes/kubernetes/pull/107406), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider]

A security issue was discovered in Kubernetes where a large number of container checkpoint requests made to the unauthenticated kubelet read-only HTTP endpoint may cause a Node Denial of Service by filling the Node's disk.

**Affected Versions**:
  - kubelet kubelet v1.30.0 to v1.30.9
  - kubelet v1.31.0 to v1.31.5
  - kubelet v1.32.0 to v1.32.1

**Fixed Versions**:
  - kubelet 1.29.14
  - kubelet 1.30.10

      .buffer()
      .writeUtf8(content)
      .close()
  }

  /**
   * A network interceptor strips the handshake from a real HTTPS response before the
   * CacheInterceptor writes it to disk. This creates the bug condition: url.isHttps=true
   * but handshake=null. Before the fix, `handshake!!` in writeTo() threw NPE.
   *
   * https://github.com/square/okhttp/issues/8962
   */
  @Test

- Kubeadm: during the validation of existing kubeconfig files on disk, handle cases where the "ca.crt" is a bundle and has intermediate certificates. Find a common trust anchor between the "ca.crt" bundle and the CA in the existing kubeconfig on disk instead of treating "ca.crt" as a file containing a single CA. ([#123102](https://github.com/kubernetes/kubernetes/pull/123102), [@astundzia](https://github.com/astundzia))...

## Changelog since v1.27.13

## Changes by Kind

### Bug or Regression

- Fixed PersistentolumeLabel providing wrong topology labels to Azure Disk PersistentVolumes when the external Azure cloud provider is used. ([#124528](https://github.com/kubernetes/kubernetes/pull/124528), [@jsafrane](https://github.com/jsafrane)) [SIG Cloud Provider]