mirror of https://github.com/k3s-io/k3s
03d352f7aa
This is a special case that both kubelet and the volume driver should support, because users might expect it. One Kubernetes mechanism to deploy pods like this is via pod affinity. However, strictly speaking the CSI spec does not allow this usage mode (see https://github.com/container-storage-interface/spec/pull/150) and there is an on-going debate to enable it (see https://github.com/container-storage-interface/spec/issues/178). Therefore this test gets skipped unless explicitly enabled for a driver. CSI drivers which create a block device for a remote volume in NodePublishVolume fail this test. They have to make the volume available in NodeStageVolume and then in NodePublishVolume merely do a bind mount (as for example in https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/blob/master/pkg/gce-pd-csi-driver/node.go#L150). |
||
|---|---|---|
| .. | ||
| BUILD | ||
| base.go | ||
| driveroperations.go | ||
| provisioning.go | ||
| snapshottable.go | ||
| subpath.go | ||
| testdriver.go | ||
| volume_io.go | ||
| volumemode.go | ||
| volumes.go | ||