release-0.19.3

What's Changed

• Fixed a possible loose of cluster state when operator has been restarted in the middle of reconcile.
• Backport of #1009
• add loadaverage + network + disk panel to clickhouse dashboard by @Slach in #1015

NOTE: There is a change in ClickHouseInstallation custom resource type, so make sure you deploy full installation manifest when upgrading.

Full Changelog: release-0.19.2...release-0.19.3

release-0.19.2

What's Changed

• Fixed a bug in 0.19.0 and 0.19.1 versions when operator could be rebuilding remote-servers.xml from scratch after restart. When it happened, distributed queries might behave unexpectedly.

Full Changelog: release-0.19.1...release-0.19.2

release-0.19.1

What's Changed

• Fixed MVs in Atomic databases support for ClickHouse versions 22.6 and above. Closes #989
• Fixed tables with '{uuid}' macro in Atomic databases for ClickHouse versions 22.6 and above.
• Fixed watch namespaces regexp by #992. Closes #991
• Added "clickhouse.altinity.com/ready: yes|no" annotations for replica services for the use by external load balancer.
• Updated podDisruptionBudget API version

Full changelog: release-0.19.0...release-0.19.1

release-0.19.0

What's Changed

• Now 'clickhouse-operator' user is restricted to an IP address of the pod where clickhouse-operator is running. It can not be used from anywhere else.
• In addition to hostRegexp, 'default' user is restricted to IP addresses of pods of the CHI. This fixes connectivity issues between shards in GKE.
• ClickHouse 'interserver_http_host' is set to the service name and matches 'remote_servers'. It can be changed to full names with 'replicasUseFQDN' setting if needed. This fixes connectivity issues between replicas in GKE.
• Changed the way schema is propagated to new shards. It is currently controlled by two cluster level settings:

  schemaPolicy:
    replica: None | All (default)
    shard: None | All (default) | DistributedTablesOnly

Previously, when adding shards only distributed tables and dependent objects were created (DistributedTablesOnly).

• Added support for adding custom CA for operator connection to ClickHouse by @SuzyWangIBMer in #930
• Fixed support of '{uuid}' macro for Atomic databases. Closes #857
• Fixed a bug when replica sometimes was not removed from ZooKeeper when scaling down the cluster
• Set container-log on ubi instead of busybox by @SuzyWangIBMer in #940
• upgrade vertamedia-clickhouse-grafana to 2.5.0 in dashboard and grafana 7.5.16 by @Slach in #951
• Improve grafana dashboards by @Slach in #952
• Improve grafana-operator + prometheus-operator by @Slach in #953

New Contributors

• @roshanths made their first contribution in #936
• @SuzyWangIBMer made their first contribution in #940
• @meob made their first contribution in #949

Full Changelog: 0.18.5...release-0.19.0

release-0.18.5

What's Changed

• Dependencies were updated to address CVE-2022-21698 and CVE-2021-38561
• generate_chart.sh by @ganievs in #925

New Contributors

• @ganievs made their first contribution in #925

Full Changelog: 0.18.4...0.18.5

release-0.18.4

What's Changed

• Base image has been updated to address https://access.redhat.com/errata/RHSA-2022:0896 (closes #913)
• Https support for health checks by @bkuschel in #912
• Fixed number of SERVERS from 1 to 3 for a 3 node clickhouse-keeper deployment by @a-dot in #902
• clickhouse-keeper and ZooKeeper manifests were updated by @Slach in #911 and #916

New Contributors

• @a-dot made their first contribution in #902
• @bkuschel made their first contribution in #912

Full Changelog: 0.18.3...0.18.4

release-0.18.3

What's Changed

• Fixed a bug that might result in broken CHI if operator has been restarted during the reconcile
• Added 'AGE' to CHI status
• Added ClickHouse Keeper examples

Full Changelog: 0.18.2...0.18.3

0.18.2

What's Changed

• Operator now correctly respects configuration settings to exclude annotations from managed objects. Fixes #859
• Make CHI status messages more human friendly

Full Changelog: 0.18.1...0.18.2

release-0.18.1

What's Changed

• fix non pointer mistake in metrics-exporter by @adu-bricks in #870
• Helper files for operatorhub.io integration

New Contributors

• @adu-bricks made their first contribution in #870

Full Changelog: 0.18.0...0.18.1

release-0.18.0

New features

• arm64 packages are published (closes #852)
• 'access_management' can be specified when defining users in CHI.
• k8s secrets can be referenced when defining user passwords. See 05-settings-01-overview.yaml.

Changed

• When CRD is deleted, operator keeps all dependent objects now (statefulsets, volumes). That prevents from incidental delete of a cluster.
• When operator restarts it does not run a reconcile cycle anymore if CHI has not been changed. That prevents unneeded pod restarts. (Closes #855)
• Operator configuration file format has been changed. See https://github.com/Altinity/clickhouse-operator/blob/0.18.0/config/config.yaml. Configuration in old format is supported for backwards compatibility.

Fixed

• Fixed a bug 'unable to decode watch event: no kind "ClickHouseOperatorConfiguration" is registered' that could appear in some k8s configurations.
• Removed INFORMATION_SCHEMA from schema propagation. (closes #854)
• Added a containerPort to metrics-exporter (#834)

New Contributors

• @johnhummelAltinity made their first contribution in #838
• @jiangxinqi1995 made their first contribution in #846
• @johnny made their first contribution in #834

Full Changelog: 0.17.0...0.18.0