Allow custom rules for (Cluster)Role to be provided/exposed in values.yaml helm chart
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 483
Description
**Description**
I may be the only one with this use-case but I would love it if I could specify the rules for pod-launcher (give it extra permissions on kube)
**Use case / motivation**
I'd like to give pod-launcher permission to create and monitor Job type as well as regular pod type.
Currently in my deployment I just apply a post-deploy patch to the ClusterRole with the added perms I want but this feels hacky to me. If there's a way to do this better please let me know!
**Are you willing to submit a PR?**
**Related Issues**
Contributor guide
Research direction
Start by reading the Helm chart's values.yaml and the ClusterRole/Role definitions that configure pod-launcher permissions. Add a values.yaml option for custom rules and verify that the configured rules are exposed in the rendered ClusterRole or Role, including permissions for Jobs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100