Add functionality to set pv gid annotation via driver volumecontext

[dankova22]

What type of PR is this?
/kind feature

What this PR does / why we need it:
We would like to add functionality to a CSI driver to be able set stricter permissions on provisioned directories, and still have this be accessible to whatever pod uses this provisioned dir. To do this, we would like to be able to dynamically assign a random gid to a provisioned dir, and add this gid as a supplemental group to any pod using this volume. We need to set the pv.beta.kubernetes.io/gid annotation in the PV metadata: https://kubernetes.io/docs/tasks/configure-pod-container/configure-persistent-volume-storage/#access-control, however this is not exposed in the CreateVolume response of CSI driver.

Therefore, we are requesting this feature of the external-provisioner that will parse VolumeContext for a gid key and apply this to the PV metadata if returned from CSI driver.
notes for your reviewer**:

Does this PR introduce a user-facing change?:

Set PV gid metadata annotation in provision workflow if gid key is returned in volume context from CSI driver

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dankova22
Once this PR has been reviewed and has the lgtm label, please assign msau42 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @dankova22!

It looks like this is your first PR to kubernetes-csi/external-provisioner 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-csi/external-provisioner has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @dankova22. Thanks for your PR.

I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[AndrewSirenko]

Having provisioner reach into volumeAttributes like this violates CSI Spec.

volumeAttributes comes from CSI CreateVolumeResponse.volume.volume_context, which according to CSI Spec shall be opaque to CO (and therefore csi-provisioner)

// Opaque static properties of the volume. SP MAY use this field to
// ensure subsequent volume validation and publishing calls have
// contextual information.
// The contents of this field SHALL be opaque to a CO.

source