Clickhouse Operator Versions Save

Altinity Kubernetes Operator for ClickHouse creates, configures and manages ClickHouse clusters running on Kubernetes

release-0.21.2

10 months ago

Added

Changed

  • Operator and metrics-exporter now automatically select 'http' or 'https' for connecting to cluster based on cluster configuration
  • Changed statefulSet update behaviour to abort the update on failure. That protects the rest of the cluster from a breaking changes
  • Removed unneeded operations on persistent volumes

Fixed

Other

New Contributors

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.21.1...release-0.21.2

release-0.21.1

11 months ago

Added

reconcile:
  runtime:
    # Max number of concurrent CHI reconciles in progress
    reconcileCHIsThreadsNumber: 10
    # Max number of concurrent shard reconciles in progress
    reconcileShardsThreadsNumber: 1
    # The maximum percentage of cluster shards that may be reconciled in parallel
    reconcileShardsMaxConcurrencyPercent: 50
  • Added default configuration for ClickHouse system.trace_log table with 30 days TTL

Changed

  • ZooKeeper manifests were rewritten to store configuration separately

Fixed

  • Fixed a bug in metrics-exporter that might stop working on ClickHouse nodes with certain types of system.errors. Closes #1161
  • Fixed a bug with ClickHouse major version detection for Altinity.Stable builds

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.21.0...release-0.21.1

release-0.21.0

11 months ago

What's Changed

  • Changed the way Operator applies ClickHouse settings. In the previous version, every change in settings required a restart via re-creating a StatefulSet. In this version it does not re-create StatefulSet anymore, but maintains a logic that decide if ClickHouse needs to be restarted in order to pickup a change or not. In case of restart it is performed using scaling stateful set down and up. The restart logic is controlled by configurationRestartPolicy configuration setting. Here is the default configuration:
    rules:
      - version: "*"
        rules:
          - settings/*: "yes"
          - settings/dictionaries_config: "no"
          - settings/logger: "no"
          - settings/macros/*: "no"
          - settings/max_server_memory_*: "no"
          - settings/max_*_to_drop: "no"
          - settings/max_concurrent_queries: "no"
          - settings/models_config: "no"
          - settings/user_defined_executable_functions_config: "no"

          - zookeeper/*: "yes"

          - files/config.d/*.xml: "yes"
          - files/config.d/*dict*.xml: "no"

          - profiles/default/background_*_pool_size: "yes"
          - profiles/default/max_*_for_server: "yes"
      - version: "21.*"
        rules:
          - settings/logger: "yes" 

Fixed

  • Fixed a bug that might result in PDB being deleted. Closes https://github.com/Altinity/clickhouse-operator/issues/1139
  • Fixed propagation of podTemplate environment variables from ClickHouseInstallationTemplate to ClickHouseInstallation
  • Fixed propagation of startup probe from ClickHouseInstallationTemplate to ClickHouseInstallation

Non-operator changes

  • Changed Grafana deployment to allow persisting custom dashboards
  • Changed ZooKeeper version to 3.8.1

New Contributors

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.20.3...release-0.21.0

release-0.20.3

1 year ago

What's Changed

  • Use alpine base image instead of UBI
  • Fix error handling when table already exists in ZooKeeper for new ClickHouse versions

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.20.2...release-0.20.3

release-0.20.2

1 year ago

What's Changed

  • Added 'hostsCompleted' to the CHI status and events
  • Changed some 'default' profile settings:
    • Enabled 'do_not_merge_across_partitions_select_final'
    • Set 'load_balancing' to 'nearest_hostname'
    • Set niceness ('os_thread_priority') to 2.
  • Improved stability of metric-exporter when some ClickHouse nodes are responding slowly
  • Changed sequence of LB service creation to avoid a situation when service exists with no available endpoints
  • Added 'secure' flag at cluster level for enabling distributed queries over TLS
  • Addressed CVEs in dependent packages

Note: datatype for 'secure' flag has been changed from boolean to String (accepting, 'true', 'yes', '1' etc.)

release-0.20.1

1 year ago

What's Changed

New Contributors

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.20.0...release-0.20.1

release-0.20.0

1 year ago

What's Changed

  defaults:
    storageManagement:
      provisioner: Operator

Fixed

New Contributors

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.19.2...release-0.20.0

release-0.19.3

1 year ago

What's Changed

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

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.19.2...release-0.19.3

release-0.19.2

1 year ago

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: https://github.com/Altinity/clickhouse-operator/compare/release-0.19.1...release-0.19.2

release-0.19.1

1 year ago

What's Changed

Full changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.19.0...release-0.19.1