Helm: Option to configure 'securityContext' for controller and plugin pods

[rafaelschreiber]

Describe the feature you'd like to have

There is no way to configure the securityContext for nodePlugin and ctrlPlugin Pods, which are generated by the 'Driver' API.

Who is the end user and what is the use case where this feature will be valuable?

Cluster Administrators who want to set the securityContext manually. In my case: My Org uses images from dhi.io and the minimal (non-dev) images run under uid 65532 which does not work.

How will we know we have a good solution? (acceptance criteria)

• Extend the drivers.csi.ceph.io API to manually configure a securityContext for nodePlugin and ctrlPlugin Pods.
• Also include these option inside values.yaml in the ceph-csi-drivers Helm chart.

Additional context

Add any other context or screenshots about the feature request here.

[Madhu-1]

@rafaelschreiber Are you running today cephcsi with non-root users? because cephcsi doesnt build non-root user container images today.

[rafaelschreiber]

@Madhu-1 No, because afaik cephcsi requires root user privileges when using kernel mounter. Problem is: dhi.io's minimal cephcsi image runs with uid 65532.

Question is: If this issue is on their side by publishing no cephcsi minimal image with user root?

[Madhu-1]

If possible to run provisioner with the non-root user and for daemonset it need to run as root user. if you are interested feel free to open a PR with required changes