cloud: Create and use a global Cost Monitor role
- Dominant language
- Python
- Stars
- 26
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
At the moment we create a per-namespace Cost Monitor role and use it in the corresponding per-namespace service account, but due to the logic of removing role, where they linger as "deleted" for a while, we get a lot of noise in the list of service accounts and roles. Consider making that role per-project, similarly to the PostgreSQL instance.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the logic that creates per-namespace Cost Monitor roles and the corresponding service accounts. Compare it with the per-project PostgreSQL instance pattern; done means a project-level role is created and used without leaving per-namespace roles behind.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100