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:
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 support@altinity.com if you have upgrade issues or any questions.