Skip to content

fix(clickstack-operators): bump clickhouse-operator-helm dep to >=0.0.5 #226

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ZeynelKoca wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(clickstack-operators): bump clickhouse-operator-helm dep to >=0.0.5 #226

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions .changeset/bump-clickhouse-operator-helm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
"helm-charts": minor
---

fix(clickstack-operators): bump clickhouse-operator-helm dependency to `>=0.0.5, <0.1.0`

The operator was pinned to v0.0.2 by a stale `Chart.lock`, not by the `~0.0.2` constraint — under Masterminds semver `~0.0.2` already permits the full `>=0.0.2, <0.1.0` range. Widening the constraint to `>=0.0.5, <0.1.0` and regenerating the lock moves the operator to the latest 0.0.x (currently v0.0.6), which includes the changes introduced in v0.0.5:

- New CRD schema with the `spec.podDisruptionBudget` field on both `ClickHouseCluster` and `KeeperCluster` (lets users override the auto-generated PDB).
- Smart default for `ClickHouseCluster` with `replicas <= 1`: `maxUnavailable=1` instead of `minAvailable=1`, so single-replica deployments no longer deadlock on node drains.
- RBAC additions (e.g. `Jobs` informer) required by the newer controller manager.

Users on `clickstack-operators` v1.0.0 cannot benefit from any of these because the published chart's lock pins the dependency to v0.0.2, and the newer binary cannot run against v0.0.2's RBAC or CRD schema.
6 changes: 3 additions & 3 deletions charts/clickstack-operators/Chart.lock
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,6 @@ dependencies:
version: 1.7.0
- name: clickhouse-operator-helm
repository: oci://ghcr.io/clickhouse
version: 0.0.2
digest: sha256:1daf572004da83b1836c8867f11198530652fee6905d4786a2d5eef87bc611cd
generated: "2026-03-04T16:52:51.068188-06:00"
version: 0.0.6
digest: sha256:07f7e26310152ee102b4d1c8d32e6211dcfaf2abdf240a1769f5490f0de2ebd7
generated: "2026-06-30T10:56:03.8831264+02:00"
4 changes: 2 additions & 2 deletions charts/clickstack-operators/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,14 +5,14 @@ description: >-
installing clickstack/clickstack to ensure CRDs are registered.
home: https://clickhouse.com/docs/use-cases/observability/clickstack
type: application
version: 1.0.0
version: 1.1.0
appVersion: "1.0.0"
dependencies:
- name: mongodb-kubernetes
version: "~1.7.0"
repository: https://mongodb.github.io/helm-charts
alias: mongodb-operator
- name: clickhouse-operator-helm
version: "~0.0.2"
version: ">=0.0.5, <0.1.0"
repository: oci://ghcr.io/clickhouse
alias: clickhouse-operator
Loading