coder-logstream-kube deployment naming conflict
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Start by reading the commit linked in the issue to find how the deployment name is derived, then inspect the Helm chart templates and values for the existing configurable RBAC names. Add a configurable deployment name or nameOverride consistent with the chart's conventions. Done means templating coder and coder-logstream-kube together no longer produces two deployments named coder.
Written by the indexing model from the issue text.
Description
Hey, we are using a wrapper chart to deploy Coder and coder-logstream-kube. Therefore, the release name of both is coder, which leads to a conflict in the name of the deployment in the new version, as https://github.com/coder/coder-logstream-kube/commit/500d0d50c40e0b3d6ced56167bce80a49d76ad44 changed the name of the deployment to the name of the release. Would it be possible, to support something like a nameOverride in coder-logstream-kube, to prevent the naming conflict and keep the deployment of Coder itself as coder or make the name of the deployment configurable as for the RBAC resources?
To reproduce:
- Create a Helm chart with coder and coder-logstream-kube as dependency charts
- Deploy or template the chart -> leads to 2 deployment with the name
coder
- Dominant language
- Go
- Stars
- 28
- Forks
- 9
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 6
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from coder/coder-logstream-kube
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
coder/coder-logstream-kube#126 · 3 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
coder/coder-logstream-kube#61 · 1 comment · 1 reaction ·
All issues in coder/coder-logstream-kube
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
coder/openstorage#807 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
kind/features
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
TencentBlueKing/bk-nodemgr#3991 ·
Maintainers usually reply within 1 day
-
meta
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
last9/last9-mcp-server#554 ·
Maintainers usually reply within 1 day