- Fixed a race condition that could result in erroneous volume unmounts for flex volume plugins during kubelet restart. ([#127669](https://github.com/kubernetes/kubernetes/pull/127669), [@olyazavr](https://github.com/olyazavr))

  
  It matches all PVC objects that have the volume attributes class mentioned. 
  

 - Kubelet flag `--keep-terminated-pod-volumes` was removed.  This flag was deprecated in 2017. ([#122082](https://github.com/kubernetes/kubernetes/pull/122082), [@carlory](https://github.com/carlory)) [SIG Apps, Node, Storage and Testing]
 
## Changes by Kind

### Deprecation

### Bug or Regression

- Added support for Pods to reference the same `PersistentVolumeClaim` across multiple volumes. ([#122140](https://github.com/kubernetes/kubernetes/pull/122140), [@huww98](https://github.com/huww98)) [SIG Node, Storage and Testing]

- Enabled kube-apiserver support for `PodCertificateRequest` and `PodCertificate` projected volumes (behind the `PodCertificateRequest` feature gate). ([#128010](https://github.com/kubernetes/kubernetes/pull/128010), [@ahmedtd](https://github.com/ahmedtd)) [SIG API Machinery, Apps, Auth, Cloud Provider, Etcd, Node, Storage and Testing]

        // Verify column metadata
        final String[] columns = extractData.getValues("columns");
        assertNotNull(columns);
        assertEquals(4, columns.length);
        assertEquals("Name", columns[0]);
        assertEquals("Email", columns[1]);
        assertEquals("Age", columns[2]);
        assertEquals("Department", columns[3]);

        // Verify row count

        final ExtractData extractData = new ExtractData(textBuilder.toString().trim());

        // Add column metadata
        if (extractColumnMetadata && headers != null) {
            extractData.putValues("columns", headers);
            extractData.putValue("column_count", String.valueOf(headers.length));
        }

        extractData.putValue("row_count", String.valueOf(rows.size()));

        return extractData;

 *
 * <p><b>Warning:</b> {@code ArrayTable} is rarely the {@link Table} implementation you want. First,
 * it requires that the complete universe of rows and columns be specified at construction time.
 * Second, it is always backed by an array large enough to hold a value for every possible
 * combination of row and column keys. (This is rarely optimal unless the table is extremely dense.)