zalando / zalando/postgres-operator
Using workload identity to make backups on Azure
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hello, by the docs and issues reviewed, for example this one, it shows that there is an option to use workload identity for GSE backups.
I was wondering, if the same could be done or the docs could show a way how to configure the same for Azure storage account based backups?
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 the linked issue 1995 and the existing documentation for workload identity with GSE backups. Then compare that setup with Azure storage account-based backups and identify whether a supported configuration or documentation change is needed; done means the Azure approach is clearly documented or its support gap is confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, kubernetes, postgresql
- Domain
- cloud, databases, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100