Altinity / Altinity/clickhouse-operator
[feature request] Ability to deploy an operator with permissions only at the namespace level
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
In continuation of this topic https://github.com/Altinity/clickhouse-operator/issues/1422.
It would be great to be able to deploy a CH operator using Helm without cluster-level permissions, but only in a specific namespace.
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
Begin with issue #1422 and the repository's Helm deployment configuration. Determine the namespace-scoped operator deployment and permissions required; done means Helm can install the ClickHouse operator in one namespace without cluster-level permissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- authorization, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100