Releases: Altinity/clickhouse-operator
release-0.11.0
New features:
- ClickHouse settings can be configured at shard/replica level
- Custom ClickHouse configuration files may be supplied both for 'users.d' and 'config.d' sections using 'users.d/my_users.xml:' syntax.
- Operator is registered as a finalizer for CHI, so CHI deletion is more reliable now.
Bug fixes:
- Operator does not attempt to create a schema when cluster is rolled over initially anymore. Fixes #479 and may improve #478 as well
- Schema creation logic when adding new shards/replicas has been improved to address #308
- Operator restart should not cause ClickHouse pods restart anymore in most cases
Important Note: CHI can not be deleted without operator installed anymore. Also, if operator and CHI is installed in one namespace, and namespace is deleted, it may stuck forever in 'Terminating' state due to an arbitrary deletion sequence.
release-0.10.0
General:
- Kubernetes APIs used by operator have been updated to 1.15. Operator does not use features from new APIs, so it keeps working with Kubernetes 1.12 and above. Operator is tested for compatibility with different k8s versions, and we did not face any issues.
New features:
- Ability to re-scale storage, both by enlarging volume size for existing installations in volumeClaimTemplate, and by adding extra volumes. That requires pod restarts.
- Operator re-creates a StatefulSet if there are changes that can not be applied to an existing object
- Configurable namespaceNamePattern and statefulSetNamePattern (#360 by @qixiaogang), see example
- New exported metrics 'metric.ChangedSettingsHash', 'metric.LongestRunningQuery' and 'active 'label for table sizes.
- Numerous improvements to Grafana dashboard
Bug fixes:
- Set 'internal_replication' to false for single replica clusters (#422 by @yuzhichang)
- Fixed schema creation logic when adding new replica (#385), improved stability in general for different types of objects
- Service selectors did not include namespace, that could lead to a conflict in multi-namespace environment. It is fixed now.
- Operator generated ClickHouse configuration files using standard names, like 'settings.xml'. It might lead to a conflict with user configuration files. Now all generated config files are prefixed with 'chop-generated-'.
Upgrade notes: When operator is upgraded from the previous version, it re-creates statefulsets and pods to ensure they match the installation. The storage should be correctly re-attached. As a side effect it ensures there are no backwards incompatibility issues between operator versions.
release-0.9.9
Bug fixes:
- Fixed ZooKeeper installation manifests that did not mount PV properly. The bug could result in ZooKeeper data loss if ZK pods were restarted.
- Fixed metrics exporter to work across multiple ClickHouse versions -- metric descriptions are temporary removed, Prometheus does not work good if those change.
Other changes:
- Bumped prometheus/golang_client to the latest version
- Added extra logging into chi status field.
release-0.9.8
Bug fixes:
- Fixed multi-threading model for proper handling or concurrent updates
- Fixed schema propagation logic to work with database names that require quoting
Other changes:
- Disabled query_thread_log by default (only applies to new instances)
release-0.9.7
Bug fixes:
- Fixed a bug with schema management queries failing at ClickHouse 20.3.+
- Fixed a bug with logging level configuration not being respected by metrics-exporter
- Fixed schema management logic to use ClickHouse pods directly bypassing LoadBalancer service
- Fixed a bug with host being deleted twice when deleting cluster or shards/replicas
Grafana dashboard has been also improved in this release.
release-0.9.6
Bug fixes:
- Sensitive data is masked now in operator logs
- Fixed a bug with replicated tables being deleted even when PVC has been retained (#314)
- Fixed a bug with annotations not being propagated to the pods (#289). Example 16-custom-labels-and-annotations-01.yaml
Documentation and examples has been updated to reflect recent changes.
release-0.9.5
Bug fixes:
- Fixed incorrect initialization of installation template in some cases
Improvements:
- Added podDistribution.scope in order to control scope of anti-affinity rules
release-0.9.4
Bug fixes:
- Fixed regression with Zookeeper configuration (#310)
- Fixed a bug in table_partitions metric export
- Removed excessive logging in metrics exporter
Improvements:
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:
- Please upgrade operator via re-installation. There are change in resource definitions.
- 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)