ironcore-dev / ironcore-dev/boot-operator
Helm Chart contains duplicate ClusterRole
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6
- Forks
- 9
- Avg merge
- 19h 5m
- Merged PRs (30d)
- 10
Description
What happened: When I try to install the helm chart with both:
metrics:
enable: true
rbac:
enable: true
It tries to render 2 ClusterRole resources with the same name boot-operator-metrics-reader.
This comes from auth_proxy_client_clusterrole.yaml and auth_proxy_client_clusterrole.yaml
What you expected to happen:
it to only be rendered once.
How to reproduce it (as minimally and precisely as possible):
just enable both in the values.
Anything else we need to know:
Environment:
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
Inspect the Helm templates named auth_proxy_client_clusterrole.yaml and render the chart with both metrics.enable and rbac.enable set to true. Confirm which paths produce boot-operator-metrics-reader, then ensure the rendered output contains only one ClusterRole with that name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 75/100