As an ARO customers, I want to be able to store my secrets into Azure Keyvault. Customers are looking to be able to take advantage of the Azure Keyvault CSI driver to mount and store the drivers into Azure keyvault

USER STORY:

What are we attempting to achieve? You might need to duplicate this a few times.

As a/an a
I want  b
So that  c

 
ACCEPTANCE CRITERIA:

What is "done", and how do we measure it? You might need to duplicate this a few times.
 
Given a
When  b
Then  c
 
CUSTOMER EXPERIENCE:

Only fill this out for Product Management / customer-driven work. Otherwise, delete it.

• Does this feature require customer facing documentation? YES/NO
  • If yes, provide the link once available
• Does this feature need to be communicated with the customer? YES/NO
  • • How far in advance does the customer need to be notified?
    • Ensure PM signoff that communications for enabling this feature are complete
• Does this feature require a feature enablement run (i.e. feature flags update) YES/NO
  • If YES, what feature flags need to change?
    • FLAG1=valueA
  • If YES, is it safe to bundle this feature enablement with other feature enablement tasks? YES/NO

BREADCRUMBS:

Where can SREs look for additional information? Mark with "N/A" if these items do not exist yet so Functional Teams know they need to create them.

• ADR: a
• Design Doc: b
• Wiki: c
• Similar Work PRs: d
• Subject Matter Experts: e
• PRD: f

NOTES:

If there's anything else to add.