8000 Move k8s client QPS and burst into the operator config by shubhamkapoor01 · Pull Request #2137 · Altinity/clickhouse-operator · GitHub
[go: up one dir, main page]

Skip to content

Move k8s client QPS and burst into the operator config - #2137

Open
shubhamkapoor01 wants to merge 2 commits into
Altinity:0.28.0from
shubhamkapoor01:operator-config-qps-burst
Open

shubhamkapoor01 wants to merge 2 commits into
Altinity:0.28.0from
shubhamkapoor01:operator-config-qps-burst

Conversation

@shubhamkapoor01
Copy link
Copy Markdown

Fixes #2045

QPS and burst can now be set as reconcile.runtime.k8sClientQPS and k8sClientBurst in the operator config file. They're read before the client is built.
The env vars still win when set, so nothing changes for current setups. 0 keeps the client-go defaults (5/10 per API group).

The keys are not in the ClickHouseOperatorConfiguration CRD on purpose: a CR is read after the client exists, so a value set there could never apply.

At startup the operator now warns when reconcileShardsThreadsNumber is above the client's QPS, env vars included.

Keeper and backup reconcile through their own controller-runtime client (20/30 by default), which sees neither this setting nor the env vars. I left them alone; happy to add them here if you want the same setting there.

The config cases fail on 0.28.0. Configs, bundles and helm values were regenerated with dev/build_manifests.sh and dev/generate_helm_chart.sh.

  • All commits in the PR are squashed.
  • The PR is made into dedicated next-release branch, not into master branch.
  • The PR is signed.

shubhamkapoor01 and others added 2 commits November 4, 2026 01:36
reconcile.runtime.k8sClientQPS and k8sClientBurst are read from the config
file before the client is built. The OPERATOR_K8S_CLIENT_QPS_LIMIT and
OPERATOR_K8S_CLIENT_BURST_LIMIT env vars still win when set, and 0 keeps the
client-go defaults.

The operator now warns at startup when reconcileShardsThreadsNumber is above
the client QPS, since one CHI can then have more shards in flight than the
client allows requests per second.

Fixes Altinity#2045

Signed-off-by: Shubham Kapoor <66124414+shubhamkapoor01@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0