Clickhouse Operator Versions Save

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

release-0.23.5

3 weeks ago

Changed

  • 'chi' label is currently added to 'clickhouse_operator_*' metrics
  • CHI annotations are now added as labels to 'chi_*' metrics
  • clickhouse-operator Helm charts are moved from 'deploy/helm' to 'deploy/helm/clickhouse-operator'

Fixed

  • Fixed a bug when nodes were not correctly excluded from remote_servers on replicated clusters with 4 or more shards, that might result in failed distributed queries and unnecessary reconciliation delays.

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.23.4...release-0.23.5

release-0.23.4

1 month ago

Changed

NOTE: There was a lot of internal refactoring related to Keeper code, but no functional changes yet. The Keeper configuration functionality will be improved in the next major release.

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.23.3...release-0.23.4

release-0.23.3

2 months ago

Changed

Fixed

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.23.2...release-0.23.3

release-0.23.2

2 months ago

What's Changed

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.23.1...release-0.23.2

release-0.23.1

2 months ago

Fixed

Improved

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.23.0...release-0.23.1

release-0.23.0

3 months ago

Added

  • Kubernetes secrets are currently supported with the standard syntax for user passwords, configuration settings, and configuration files, for example:
    users:
      user1/password:
        valueFrom:
          secretKeyRef:
            name: clickhouse_secret
            key: pwduser1
    settings:
      s3/my_bucket/access_key:
        valueFrom:
          secretKeyRef:
            name: s3-credentials
            key: AWS_ACCESS_KEY_ID
    files:
      server.key:
        valueFrom:
          secretKeyRef:
            name: clickhouse-certs
            key: server.key

See updated Security Hardening Guide for more detail.

kind: ClickHouseKeeperInstallation

See examples in there: https://github.com/Altinity/clickhouse-operator/tree/0.23.0/docs/chk-examples The implementation is not final, following things yet needs to be done:

  1. dynamic reconfiguration, that is required in order to support adding and removing Keeper replicas
  2. integration with ClickHouseInstallation, so Keeper could be referenced by a reference, instead by a service
  • CHI labels are now added to exported Prometheus metrics

Changed

  • Services are now re-created if ServiceType is changed in order to workaround Kubernetes issue. Closes https://github.com/Altinity/clickhouse-operator/issues/1302
  • Operator now waits for ClickHouse service endpoints to respond when checking node is up.
  • CHI templates are now automatically reloaded by operator. Before, templates were only reloaded during startup. In order to apply changes, CHI update needs to be triggered.
  • Operator will now crash if operator configuration is broken or can not be parsed. That prevents the fallback to the defaults in case of errors.

Fixed

Improved

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.22.2...release-0.23.0

release-0.22.2

4 months ago

What's Changed

  • Fixed a bug when operator did not restart ClickHouse pods if 'files' section was changed without 'config.d' destination, e.g. files/settings.xml.
  • Fix ServiceMonitor endpoints #1276 by @MiguelNdeCarvalho, and #1290 by @muicoder. Closes #1287
  • Disabled prefer_localhost_replica in default profile

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.22.1...release-0.22.2

release-0.22.1

5 months ago

Added

  • New 'Aborted' status for CHI is set when reconcile is aborted by an operator

Changed

  • Allow shard weight to be zero (#1192 by maxistua)
  • Removed excessive logging for pod update events
  • Removed 30s delay after creating a service
  • Allow empty values for CRD status and some other fields in order to facilitate migration from old operator versions that were upgraded without upgrading CRD first. Fixes #842, #890 and similar issues.

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.22.0...release-0.22.1

release-0.22.0

6 months ago

Added

  • Support volume re-provisioning. If volume is broken and PVC detects it as lost, operator re-provisions the volume
  • When new CHI is created, all hosts are created in parallel
  • Allow to turn off waiting for running queries to complete. This can be done both in operator configuration or in CHI itself: In operator configuration:
spec:
  reconcile:
    host:
      wait:
        queries: "false"

In CHI:

spec:
  reconciling:
    policy: nowait
  • When changes are applied to clusters with a lot of shards, the change is probed on a first node only. Is successul, it is applied on 50% of shards. This can be configured in operator configuration:
reconcile:
  # Reconcile runtime settings
  runtime:
    # Max number of concurrent CHI reconciles in progress
    reconcileCHIsThreadsNumber: 10

    # The operator reconciles shards concurrently in each CHI with the following limitations:
    #   1. Number of shards being reconciled (and thus having hosts down) in each CHI concurrently
    #      can not be greater than 'reconcileShardsThreadsNumber'.
    #   2. Percentage of shards being reconciled (and thus having hosts down) in each CHI concurrently
    #      can not be greater than 'reconcileShardsMaxConcurrencyPercent'.
    #   3. The first shard is always reconciled alone. Concurrency starts from the second shard and onward.
    # Thus limiting number of shards being reconciled (and thus having hosts down) in each CHI by both number and percentage

    # Max number of concurrent shard reconciles within one CHI in progress
    reconcileShardsThreadsNumber: 5
    # Max percentage of concurrent shard reconciles within one CHI in progress
    reconcileShardsMaxConcurrencyPercent: 50
  • Operator-related metrics are exposed to Prometheus now:
clickhouse_operator_chi_reconciles_started
clickhouse_operator_chi_reconciles_completed
clickhouse_operator_chi_reconciles_timings

clickhouse_operator_host_reconciles_started
clickhouse_operator_host_reconciles_completed
clickhouse_operator_host_reconciles_restarts
clickhouse_operator_host_reconciles_errors
clickhouse_operator_host_reconciles_timings

clickhouse_operator_pod_add_events
clickhouse_operator_pod_update_events
clickhouse_operator_pod_delete_events

Changed

Fixed

  • Fixed a bug when operator could break multiple nodes if incorrect configuration has been deployed several times in a row
  • Fixed a bug when schema could not be created on new nodes, if nodes took too long to start
  • Fixed a bug when services were not reconciled in rare cases

New Contributors

Full Changelog: https://github.com/Altinity/clickhouse-operator/compare/release-0.21.3...release-0.22.0

release-0.21.3

9 months ago

Added

Changed

  • CHITemplates are now re-loaded automatically without a need to restart operator. Changes in CHITemplates are not applied automatically to affected CHI.

Fixed

New Contributors

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