API-1690: KMS Encryption Provider for Etcd Secrets

[swghosh]

[TP] Support Kube KMS Integration in OCP (User-Provided)

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign zaneb for approval. For more information see the Kubernetes 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

[openshift-ci-robot]

@swghosh: This pull request references API-1690 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.18.0" version, but no target version was set.

In response to this:

[TP] Support Kube KMS Integration in OCP (User-Provided)

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 openshift-eng/jira-lifecycle-plugin repository.

[swghosh]

/cc @dgrisonnet

[JoelSpeed]

@tkashem should be the default approver for anything api related as the team lead

You can add either myself or @deads2k for API approvers. But you need one of us. I've already looked at the API so probably me on this occasion.

@tkashem please review this EP and let me know that you're happy conceptually, and then I'll start reviewing from an API perspective

We should only merge the feature gate PR once this has had an initial round of review

[swghosh]

Will add more details on this EP so we can have it ready for the initial round of review.