release-0.9.3

Bug fixes:

• Fixed a problem with upgrading operator for ClickHouseInstallations created by operator 0.8.0 and earlier
• Fixed a problem with updates to ClickHouse users configuration not always being propagated to ClickHouse servers (#282 )

Tweak:

• Added operator log level configuration

IMPORTANT NOTES:

1. Please upgrade operator via re-installation. There are change in resource definitions.
2. Operator versions 0.9.1 and 0.9.2 are not compatible with 0.9.0 and 0.9.3 in regards to upgrade. Clusters created with those versions have to be re-created.

release-0.9.2

Bug fixes:

• Fixed memory leak in metrics exporter (#176)

release-0.9.1

Bug fixes:

• Fixed regression with 'files' section of configuration (#261)
• Fixed discovery of monitored ClickHouse clusters by metrics exporter when it is being restarted (#239)

release-0.9.0

New features:

• Option to define template per ClickHouse replica (before it was only possible to have global, shard based or
• 'circular' replication shortcut (podDistribution.type: CircularReplication)
• hostTemplates in order to propagate custom ports across configuration
• hostNetwork support and portDistribution types. See examples starting from '14-' in examples folder.
  host based templates)
• New Grafana dashboard

release-0.8.0

New features:

• Introduced a set of 'podDistribution' affinity/anti-affinity rules to manage pod deployment in ClickHouse terms. See https://github.com/Altinity/clickhouse-operator/blob/master/docs/chi-examples/10-zones-03-advanced-03-pod-per-host-default-storage-class.yaml
• Default security configuration is improved:
  • All networks are disabled now. Localhost connections are enabled.
  • Connections from the cluster nodes are enabled via host_regexp.
  • ClickHouse user passwords are automatically hashed sha256 and stored as password_sha256_hex in config maps and files.
• All operator and user labels are propagated from ClickHouseInstallation to dependent objects: statefulsets, pods, services and configmaps
• Added some ClickHouse defaults that are automatically applied. It can be changed in operator configuration if necessary. See:
  • https://github.com/Altinity/clickhouse-operator/tree/master/config/config.d
  • https://github.com/Altinity/clickhouse-operator/tree/master/config/users.d
  • https://github.com/Altinity/clickhouse-operator/blob/master/config/config.yaml

Monitoring improvements:

• ClickHouse mutations are now available in monitoring
• Metrics fetch/error events were added
• Fixed a bug with monitoring events not properly labeled (also fixes #225)
• Fixed a bug when all hosts were dropped out of monitoring if one host fails

Other bug fixes:

• Fixed a bug when schema could not be created automatically on newer versions of ClickHouse (#227).
• Fixed a bug with zookeeper root entry not propagated to ClickHouse configuration

Upgrade notes:

• There were changes in ClickHouseInstallation CRD. It is recommended to remove and re-install the operator. Existing ClickHouse clusters will be picked up automatically.
• IMPORTANT: If you upgrade operator from 0.6.0 or earlier to 0.8.0 please make sure your ClickHouseInstallation name is shorter than 15 symbols. Otherwise DO NOT UPGRADE an operator.

Please contact [email protected] if you have upgrade issues or any questions.

release-0.7.0

New features:

• Added 'podVolumeClaimTemplate' and 'logVolumeClaimTemplate' in order to map data and logs separately. Old syntax is deprecated but supported.
• Sidecar clickhouse-logs container to view logs if persistent volume is used
• Significantly cleaned up templates model and 'useTemplates' extension
• new system_replicas_is_session_expired monitoring metric (#187 by @teralype)

Bug fixes:

• Fixed bug with installation name being truncated to 15 chars. The current limit is 60 chars. Cluster name is limited to 15.
• General stability improvements and fixes for corner cases

Upgrade notes:

• There were changes in ClickHouseInstallation CRD, so it is recommended to remove and re-install the operator. Existing ClickHouse clusters will be picked up automatically.
• IMPORTANT: If you upgrade operator from 0.6.0 or earlier to 0.7.0 please make sure your ClickHouseInstallation name is shorter than 15 symbols. Otherwise DO NOT UPGRADE an operator.

Please contact [email protected] if you have upgrade issues

release-0.6.0

New features:

• Added spec.stop property to start/stop all ClickHouse pods in installation for maintenance
• ClickHouseInstallationTemplate custom resource definition
• ClickHouseOperatorConfiguration custom resource definition

Improvements:

• Split operator into two binaries/containers - operator and metrics monitor
• Added 10s timeout to ClickHouse connection
• Improved create/update logic
• Operator now looks at its own namespace if not specified explicitly
• Enhance multi-thread support for concurrent operations

Improvements in documentation and examples.

release-0.5.0

This release mainly simplified installation and management in different environments.

New features:

• Specify watched namespace(s) with WATCH_NAMESPACE and WATCH_NAMESPACES env vars
• Pack operator's configuration into Docker image, so it can be installed without complicated manifest
• ClickHouseInstallationTemplate CRD for providing configuration templates at the operator level
• Supported verbosity levels for ClickHouseInstallation resource information returned by kubectl get

Improvements:

• Clarify docs and examples
• Update Prometheus handler to up-to-date state

Bug fixes:

• Fix clickhouse-operator-install.sh

release-0.4.4

Bug fixes:

• Fixed a bug with is_local not being properly initialised on pod startup. Fixes #138
• Allowed updating annotations of service templates

release-0.4.3

New features:

• Support for extra properties in ZooKeeper configuration
• Support for custom XML files included in the configuration
• Automatic ClickHouse restarts when 'settings' are modified

Improvements:

• Cleaned up logging
• Fixed processing of non-string ClickHouse settings