[bug]: v0.0.12 helm chart now requires that you pass in your own namespace
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- helm, kubernetes
- Domain
- authorization, devops
Research direction
Review PR #124 and the Helm chart templates that define namespaces, RBAC resources, and environment variables. Compare namespace-scoped and cluster-scoped deployments, then verify that an unset or explicit rbacScope produces the corresponding Role/RoleBinding or ClusterRole/ClusterRoleBinding behavior without requiring per-namespace values files.
Written by the indexing model from the issue text.
Description
In https://github.com/coder/coder-logstream-kube/pull/124 you now must pass in your own namespace as a parameter to the helm chart if you don't want to create a ClusterRole and ClusterRoleBinding. This is rough from a GitOps perspective, because it means that you have two choices (in an environment where applications are not allowed to create cluster-scoped resources):
- You create
values.<something>.yamlfiles where you setnamespaces: [ my-coder-ns ]and launch the application with custom values files for each namespace you put it in. - When you launch the application you pass in
--set namespaces=...
In my opinion, if namespaces is not set, then there should be a simple setting of rbacScope: <namespace|cluster> ... and if it is set to namespace then the RBAC permissions created with Role/RoleBindings (and NAMESPACES=${{ .Release.Namespace}} is set as an env variable). If it is set to cluster, then you create ClusterRole/ClusterRoleBindings.
- 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 2/5 1-3 hours Newbie friendliness 68/100
coder/coder-logstream-kube#255 · 1 comment ·
-
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