Allow for custom keyvault secrets to be injected as k8s env vars
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
This needs to happen after https://github.com/rstudio/ptd/issues/1957 is complete for Azure workloads, AWS can happen anytime.
Need to allow for custom secrets in Secrets Manager or Key Vault to be injected into pods as environment variables/k8s secrets. This would be used for Workbench (and/or connect?) session pods to be accessible inside the session.
Notify Azure customer once this has been done:
https://positpbc.atlassian.net/browse/PTDC-19
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 reading linked issue 1957 and locating how Workbench or Connect session pods currently receive secrets. Compare the AWS Secrets Manager and Azure Key Vault requirements, then verify that custom secrets are available inside pods as environment variables or Kubernetes secrets; notify the Azure customer when complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, go, kubernetes
- Domain
- cloud, devops, infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100