VictoriaMetrics / VictoriaMetrics/operator
Allow VMAlert CRD to store s3 credentials in kubernetes secret
Open
Nobody has claimed this yet.
docs
good first issue
question
- Dominant language
- Go
- Stars
- 589
- Forks
- 229
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 77
Description
I would like the ability to store the access key and key_id as a kubernetes secret similar to how it is done in backup manager. It would nice if CustomS3Enpoint was also added so specifying a custom is consistent across CRDs
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 locating the VMAlert CRD definition and the backup manager's Kubernetes Secret handling, then inspect the related operator entry points and tests. The work is done when VMAlert supports Secret-based access credentials and a custom S3 endpoint consistently with the other CRDs, with coverage for those settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100