This feature installs platform CSI drivers so they support
SELinuxMountReadWriteOncePod. This assumes the operating system on all
nodes supports SELinux!
The hook can cause issue on execution, like
```
Exec lifecycle hook ([/bin/sh -c rm -rf
/registration/ebs.csi.aws.com-reg.sock /csi/csi.sock]) for Container
"node-driver-registrar" in Pod
"ebs-csi-node-96jbk_ebs-csi(a82c6d41-bd2b-42dd-b092-e3acd4c43b62)"
failed - error: command '/bin/sh -c rm -rf
/registration/ebs.csi.aws.com-reg.sock /csi/csi.sock' exited with 126: ,
message: "OCI runtime exec failed: exec failed: container_linux.go:370:
starting container process caused: exec: \"/bin/sh\": stat /bin/sh: no
such file or directory: unknown\r\n"
```
Moreover, it has been deleted from upstream driver, see this patch
6e59160eea
Signed-off-by: Nicolas Sterchele <foss@sterchelen.net>
This manifest includes two liveness-probe containers but they use different images.
The k8s.gcr.io image is multi-arch but the quay.io image is not.
By only using the k8s.gcr.io one we should fix arm64 clusters now that EBS CSI is enabled by default.
- Update manifests
- Bump components version
- Add API capability of setting Version + VolumeLimit
- Remove snapshot-controller resources as it should be independent from
any CSI driver
Signed-off-by: dntosas <ntosas@gmail.com>