Bug: Driver must run as root
Summary
After experimentation, Node Driver Registrar must run as root for any CSI interface to properly attach volumes to hosts.
Steps to reproduce
Deploy any CSI implementation (EBS CSI driver or other, all of which require this image) and see that the pods do not correctly deploy.
What is the current bug behavior?
Pods running with the csi-node-driver-registrar will fail to fully come up properly. They will not be able to correctly run.
What is the expected correct behavior?
EBS CSI driver should be able to come up and allow for volume attachment.
Relevant logs and/or screenshots
Normal WaitForFirstConsumer 45s persistentvolume-controller waiting for first consumer to be created before binding
Normal ExternalProvisioning 14s (x5 over 45s) persistentvolume-controller waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
Normal Provisioning 14s (x6 over 45s) ebs.csi.aws.com_ebs-csi-controller-67dc48cfcb-g9jjd_3215ee3f-de13-418d-9f77-aa3c20c66852 External provisioner is provisioning volume for claim "logging/elasticsearch-data-logging-ek-es-data-0"
Warning ProvisioningFailed 14s (x6 over 45s) ebs.csi.aws.com_ebs-csi-controller-67dc48cfcb-g9jjd_3215ee3f-de13-418d-9f77-aa3c20c66852 failed to provision volume with StorageClass "standard": error generating accessibility requirements: no topology key found on CSINode ip-146-69-210-138.us-gov-east-1.compute.interna
Run as root user was the only fix we found that allowed it to work.
Defintion of Done
-
Bug has been identified and corrected within the container