pkg log/syslog (darwin-arm64), method (*Writer) Emerg(string) error
pkg log/syslog (darwin-arm64), method (*Writer) Err(string) error
pkg log/syslog (darwin-arm64), method (*Writer) Info(string) error
pkg log/syslog (darwin-arm64), method (*Writer) Notice(string) error
pkg log/syslog (darwin-arm64), method (*Writer) Warning(string) error
pkg log/syslog (darwin-arm64), method (*Writer) Write([]uint8) (int, error)

	Read(p []byte) (n int, err error)
	Close() error
}

type Writer interface {
	Write(p []byte) (n int, err error)
	Close() error
}

// ReadWriter's methods are Read, Write, and Close.
type ReadWriter interface {
	Reader  // includes methods of Reader in ReadWriter's method set
	Writer  // includes methods of Writer in ReadWriter's method set
}
</pre>

<p>

feature gate is enabled, user should not upgrade to Kubernetes v1.22. vSphere CSI Driver does not support Kubernetes v1.22 yet because it uses v1beta1 CRD APIs. Support for v1.22 will be added at a later release. Check the following document for supported Kubernetes releases for a given [vSphere CSI Driver version](https://vsphere-csi-driver.sigs.k8s.io/compatiblity_matrix.html#compatibility-matrix-for-vsphere-csi-driver).

### Workloads that saturate nodes with pods may see pods that fail...

g, int); public Throwables$State processLine(String); } org/junit/internal/TextListener.class package org.junit.internal; public synchronized class TextListener extends org.junit.runner.notification.RunListener { private final java.io.PrintStream writer; public void TextListener(JUnitSystem); public void TextListener(java.io.PrintStream); public void testRunFinished(org.junit.runner.Result); public void testStarted(org.junit.runner.Description); public void testFailure(org.junit.runner.notification.Failure);...

    * --google-json-key
    * --log_cadvisor_usage
    * --machine_id_file
    * --storage_driver_user
    * --storage_driver_password
    * --storage_driver_host
    * --storage_driver_db
    * --storage_driver_table
    * --storage_driver_secure
    * --storage_driver_buffer_duration

([#57613](https://github.com/kubernetes/kubernetes/pull/57613), [@mtaufen](https://github.com/mtaufen))

message CSIVolumeSource {
  // driver is the name of the CSI driver that handles this volume.
  // Consult with your admin for the correct name as registered in the cluster.
  optional string driver = 1;

  // readOnly specifies a read-only configuration for the volume.
  // Defaults to false (read/write).
  // +optional
  optional bool readOnly = 2;

  as it requires installation of AzureFile CSI Driver. Users should enable CSIMigration and
  CSIMigrationAzureFile features and install the [AzureFile CSI Driver](https://github.com/kubernetes-sigs/azurefile-csi-driver)
  to avoid disruption to existing Pod and PVC objects at that time. Azure File CSI driver does not support using same persistent

- This release enables in-tree RBD migration to CSI driver with a couple of feature gates.  These featuregates are alpha in this release.

  - `CSIMigrationRBD`: when enabled, it will redirect traffic from in tree rbd plugin ( kubernetes.io/rbd )  to CSI driver ( rbd.csi.ceph.com) , default to `false` now.
  - `IntreePluginRBDUnregister`: Disables the RBD in-tree driver

  The feature gates can be enabled by:

## Known Issues

- Unlocked the `CSIMigrationvSphere` feature gate.
  The change allow users to continue using the in-tree vSphere driver,pending a vSphere
  CSI driver release that has with GA support for Windows, XFS, and raw block access. ([#116342](https://github.com/kubernetes/kubernetes/pull/116342), [@msau42](https://github.com/msau42)) [SIG Storage]