Release Notes for starrocks-kubernetes-operator v1.8.5
We are pleased to announce the release of starrocks-kubernetes-operator v1.8.5. This release includes several bug fixes
and enhancements. Here are the key updates:
What's New
- [Chart] Service Account Customization: The operator now supports to provide the ability to add custom
annotations and labels. The previousoperator.global.rbac.serviceAccountNamefield is no longer supported. - [Operator] Explicit Protocol Selection for Istio: To provide additional functionality such as routing and rich
metrics, Istio needs to determine the protocol of the traffic. This is now achieved by automatically adding the
appProtocol field. This enhancement is particularly important for "server-first" protocols like MySQL, which are
incompatible with automatic protocol detection and may cause connection failures.
Bug Fixes
- Fixed an issue that occurred when
starrocks.initPassword.enabledis true and the value
ofstarrocks.starrocksCluster.nameis set. The FE service domain name would follow the set value, while the initpwd
pod would still use thestarrocks.nameOverridevalue to compose the FE service domain name. This fix ensures
consistent hostname usage.
Notes for Deployed Users
If starrocks.starrocksCluster.name is not set, the result of helm template will remain the same as before. If
starrocks.starrocksCluster.name is set and is different from the value of starrocks.nameOverride, the old configmaps
for FE, BE, and CN will be deleted. New configmaps with the new name for FE, BE, and CN will be created. This may
result in the restart of FE/BE/CN pods.
We encourage you to update to this new version and benefit from these improvements. As always, your feedback is very
welcome.
Changes
- [Bugfix] remove chart function kube-starrocks.name @yandongxiao (#292)
🚀 Features
- [Enhancement] add appProtocol in fe service @yandongxiao (#288)
- [Enhancement] create serviceaccount by default, and add ability to provide custom a… @AdamStaudt (#291)