Refactor secrets for azure
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
The Azure secrets store csi provider does not support JSON parsing like the AWS one does. We will need to store our secrets as separate objects in KeyVault instead of one secret object as is currently configured. (Or find some other smart way to do this, but I'd rather just use out-of-the-box add-ons as built if possible.)
Currently, the team-operator builds the SecretProviderClass CRDs for each of the workloads. These will need to be built for Azure as well, to correspond to the above individual secret objects in KeyVault.
https://github.com/Azure/secrets-store-csi-driver-provider-azure/issues/885
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the team-operator currently builds SecretProviderClass CRDs for workloads and compare that behavior with the Azure secrets-store CSI provider and Key Vault requirements. Read the linked provider issue for the JSON-parsing limitation. Done means Azure workloads reference separate Key Vault secret objects through correctly generated CRDs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100