cert-manager-csi-driver support #4495
Description
Describe the feature you are requesting
Currently, the helm chart does not allow for use cases involving cert-manager-csi-driver. There is no way to both turn off both the cert manager integration (Certificate CR) and the secret/volume/volume mount. Secondly, there is not way to overwrite or add to the annotations on the ValidatingWebhookConfiguration and MutatingWebhookConfiguration, to specify an alternate CA for injection. This feature would introduce some helm values to allow users to turn off the certificate generation when not using the built-in cert manager integration, allow users to pass in custom annotations to the webhooks, and allow users to optionally not deploy the hard coded volume and volume mounts to the certificate path.
Motivation
In order to use cert-manager-csi-driver, I should be able to have the cert volume not be from a secret, or use my own cert volume like so. I should also be able to add annotations to the webhook configs, as currently they are tightly integrated with the certs that are deployed via the secret. This will allow users more options for configuring TLS certs. Being able to use the cert-manager-csi-driver, or similar is more secure than having the secrets stored in the cluster,
Describe alternatives you've considered
Contribution Intention (Optional)
-[X] Yes, I am willing to contribute a PR to implement this feature
-[ ] No, I cannot work on a PR at this time