Altinity / Altinity/clickhouse-operator
[Request] Add support for resources on the clickhouse-logs container
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
We are currently using the ClickHouse Server Helm chart with the operator enabled (https://github.com/Altinity/helm-charts/tree/main/charts/clickhouse). However, we are unable to set resource limits for the clickhouse-logs container, and our Kubernetes cluster requires all containers to have resource requests and limits defined.
Could you please add support for this?
Thank you!
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
Start with the ClickHouse Helm chart linked in the issue and locate how the clickhouse-logs container is defined and configured. Trace the chart values and rendered Kubernetes manifest, then verify that resource requests and limits can be supplied for that container and appear in the rendered output.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100