prometheus / prometheus/alertmanager
Add authorization subsystem for Alertmanager
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
Proposal
Alertmanager is effectively a multi-tenant piece of software. However, it has no mechanism for authorization requests.
For API v3 (and Alertmanager 1.0) we should develop a mechanism for authentication and authorization of requests. Most likely, authorization can be offloaded to an authorization webhook so that users can provide their own policy engines.
The idea is to have something similar to K8s authorization webhooks: https://kubernetes.io/docs/reference/access-authn-authz/webhook/
Contributor guide
No contributing guide indexed for this repository
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
No repository files or tests are named. Start by reviewing the API v3 and Alertmanager 1.0 request-handling paths, then compare the proposal with Kubernetes authorization webhooks; the work is complete when an agreed authorization mechanism and webhook policy behavior are implemented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100