Altinity Kubernetes Operator 0.19.0 Release Notes

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 https://github.com/Altinity/clickhouse-operator/pull/930

• Fixed support of ‘{uuid}’ macro for Atomic databases. Closes https://github.com/Altinity/clickhouse-operator/issues/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 https://github.com/Altinity/clickhouse-operator/pull/940

• upgrade vertamedia-clickhouse-grafana to 2.5.0 in dashboard and grafana 7.5.16 by @Slach in https://github.com/Altinity/clickhouse-operator/pull/951

• Improve grafana dashboards by @Slach in https://github.com/Altinity/clickhouse-operator/pull/952

• Improve grafana-operator + prometheus-operator by @Slach in https://github.com/Altinity/clickhouse-operator/pull/953

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/0.18.5...release-0.19.0

Download at: https://github.com/Altinity/clickhouse-operator/releases/tag/release-0.19.0