v1.9.3 🌈

v1.9.3

Release Notes for starrocks-kubernetes-operator v1.9.3

We are excited to announce the release of StarRocks Kubernetes Operator v1.9.3. This version brings a mix of
enhancements and bug fixes to further improve the deployment and management of StarRocks clusters on Kubernetes
environments.

Enhancements

• [Operator] Enhanced Lifecycle Management: Users can now define postStart and preStop lifecycle hooks for
  StarRocksCluster, enabling more control over the cluster's lifecycle events. PR #456
• [Operator] HostPath Support: This version introduces support for hostPath, allowing users to mount local directories
  to the StarRocksCluster. PR #451
• [Chart] Scoped Permissions: The operator's permissions can now be restricted to a single namespace, enhancing security
  by limiting the operator's scope to deploying StarRocks within a designated namespace. PR #446
• [Chart] Init-Password Job Enhancements: Support for annotations and specifying the image field for the init-password
  job has been added, allowing for greater customization. PR #454
• [Operator] Configuration Flexibility: The operator now supports be_http_port and be_port in the configuration. PR #450

Bug Fixes

• [Operator] HPA Deletion Issue Resolved: A bug where the Horizontal Pod Autoscaler (HPA) was not properly deleted when
  the autoScalingPolicy field was removed has been fixed, ensuring clean and accurate scaling operations. PR #444
• [Chart] Init-Password Job Port Configuration: The query port can now be configured in the init-password job,
  addressing previous limitations and enhancing setup flexibility. PR #455

v1.9.2 🌈

Release Notes for starrocks-kubernetes-operator v1.9.2

We are excited to announce the release of StarRocks Kubernetes Operator v1.9.2. This version brings a mix of new
features, enhancements, documentation updates, and bug fixes to further improve the deployment and management of
StarRocks clusters on Kubernetes environments.

What's New

• [chart] Add Datadog profiling to SR Helm to enhance monitoring capabilities. #437
• [chart] Add starrocksCluster.componentValues to define some values uniformly to streamline configurations. #425
• [operator] Add k8s event information during the Operator reconciliation for better debugging and operational insights. #391

Enhancements

• [operator] Prefer to use containerPort to export service node port. #421
• [chart] Upgrade ServiceMonitor
  1. In order to support StarRocks Grafana Dashboard, app_starrocks_ownerreference_name or app_kubernetes_io_component labels were added to up metrics by ServiceMonitor. #433
  2. Users can now add labels on ServiceMonitor for more flexible monitoring configuration. #432
• [chart] Allow users to specify mount paths, providing more customization options for deployments. #428
• [chart] Eliminate Helm warnings caused by differing types of feEnvVars, beEnvVars, and cnEnvVars, improving the deployment experience. #434 #396
• [chart] Complete imagePullSecrets and affinity fields for helm charts to enhance deployment flexibility and scheduling. #417

Bug Fixes

• [chart] Allowed to remove some resources limit, like CPU, providing more flexibility in resource management. #426
• [chart] Upgraded the version of Golang and libraries to fix some vulnerabilities, improving security. #415

Documentation

• Added doc/least_permission_to_deploy_starrocks_howto.md to help users deploy with minimal permissions. #431
• Added more details about Prometheus integration for better monitoring setup. #427
• Removed the 1.7.0 and 1.6.x version in index.yaml. #435
• Documentation improvements including moving and adding pull request templates for better contribution guidelines. #410 #409

We thank our community for their contributions and feedback. For a detailed list of changes and updates, please refer to
the GitHub repository. Happy deploying!

v1.9.1 🌈

v1.9.1

Release Notes for starrocks-kubernetes-operator v1.9.1

We are thrilled to announce the release of StarRocks Kubernetes Operator v1.9.1. This release introduces several
enhancements and bug fixes to improve the user experience of deploying and managing StarRocks
clusters on Kubernetes.

What's New

There are enhancements in this release.

1. [chart] When you set logStorageSize to 0, the operator will not create PVC for log storage #398.
2. [operator] Checked volumes and mount paths to avoid duplication error #388
3. [operator] Disabled FE scale to 1 #394
4. [operator] Supported use of map to define feEnvVars/beEnvVars/cnEnvVars to merge on multiple values files (#396)
5. [operator] exposed spec.containers.securityContext.capabilities for user to customize the capabilities of containers. #404

BugFix

1. [operator] Supported to update service annotations fields #402 #399
2. [operator] Switched to using patch method instead of update method to modify statefulset and deployment #397.
   This solves the problem that when CN + HPA is enabled, upgrading CN will cause all CN pods to be terminated and
   restarted.
3. [operator] Switched to using Patch method instead of Update to modify service object #387. This solves the
   problem that when cloud provider is used, the service object will be modified by cloud provider, and the operator
   will overwrite the modification.
4. [operator] Considered Cn Replicas when calculating component hash #392
5. [chart] Corrected typo in storageSpec #385

v1.9.0 🌈

Release Notes for starrocks-kubernetes-operator v1.9.0

We are thrilled to announce the release of StarRocks Kubernetes Operator v1.9.0. This release introduces several
enhancements, bug fixes, and documentation updates to improve the user experience of deploying and managing StarRocks
clusters on Kubernetes.

What's New

1. [Feature] Add StarRocksWarehouse CRD to support StarRocks Warehouse Feature (#323). Note: warehouse is an
   enterprise feature for StarRocks.
2. [Enhancement] Use StarRocksCluster State to log errors when subController apply failed (#359): We have improved error
   logging by using the StarRocksCluster status.State when the subController apply operation fails.
3. [Enhancement] Support to mount emptyDir in storageVolumes (#324): We have added support to mount emptyDir in
   storageVolumes.

BugFix

1. [BugFix] We have fixed an issue where the cluster status phase was not in sync with the component.(#380)
2. [BugFix] We have fixed an issue where the HPA was not removed when the autoScalingPolicy was removed.(#379)
3. [BugFix] We have fixed an issue where the HPA resource was not removed when the CN spec was removed.(#357)

Maintenance

1. We have improved the setup of the Kubernetes environment for unit tests by using setup-envtest. (#347)
2. We have added unit tests and ensured that the code coverage is at least 65%. (#354)
3. We have updated the script to generate the API reference documentation.(#350)
4. We have switched to using zap as the logger for better logging capabilities.(#341)

We encourage you to update to this new version and benefit from these improvements. As always, your feedback is very
welcome.

v1.8.8 🌈

Release Notes for starrocks-kubernetes-operator v1.8.8

We are pleased to announce the release of starrocks-kubernetes-operator v1.8.8.

BugFix

1. When add annotations by spec.StarRocksFeSpec/StarRocksBeSpec/StarRocksCnSpec.service field, Operator should not
   annotate on search(internal) service. see #370

We encourage you to update to this new version and benefit from these improvements. As always, your feedback is very
welcome.

v1.8.7 🌈

Release Notes for starrocks-kubernetes-operator v1.8.7

We are pleased to announce the release of starrocks-kubernetes-operator v1.8.7. This release includes several updates
and improvements that enhance the functionality and usability of the StarRocks Kubernetes Operator.

Enhancement

1. Added failure seconds for liveness and readiness. When StarRocks is under heavy load, the default Liveness Probe and
   Readiness Probe may fail, causing the container to restart. This update mitigates this issue by adding failure
   seconds for liveness and readiness.

Maintenance

1. [Documentation] Updated README.md and README_ZH-CN.md. This update provides more accurate and comprehensive
   information about StarRocks Operator.
2. [Documentation] Added local_installation_how_to.md for users. This guide provides step-by-step instructions for local installation
   of the Operator and StarRocks Cluster. And it also provides a script to help users install the Operator and StarRocks Cluster locally.

We encourage you to update to this new version and benefit from these improvements. As always, your feedback is very
welcome.

Changes

• [Chore] change related fields to release v1.8.7 @yandongxiao (#312)
• [Documentation] update README_ZH-CN.md @yandongxiao (#311)
• [Documentation] update README.md @yandongxiao (#310)
• [Enhancement] add failure seconds for liveness and readiness @yandongxiao (#309)
• [Documentation] add local installation how to.md for chinese users @yandongxiao (#307)
• [Chore] Improve helm repo update command @yandongxiao (#306)

v1.8.6 🌈

Release Notes for starrocks-kubernetes-operator v1.8.6

We are pleased to announce the release of starrocks-kubernetes-operator v1.8.6. This release includes several bug fixes
and enhancements. Here are the key updates:

Bug Fixes

1. Fix the problem of nginx sending the request body to FE when redirecting the stream load request, which may cause
   the stream load to fail. (#303)

Maintenance

1. [Documentation] add doc/load_data_using_stream_load.md. This document introduces how to load data from outside the
   k8s network to StarRocks through fe-proxy.
2. [Documentation] update change_root_password_howto.md. This document adds the steps of how to update the
   root password through Helm Chart.
3. [Chore] Add GitHub Actions to add label on issue and PR. This chore improves the project quality by adding necessary
   labels to issues and PRs.

We encourage you to update to this new version and benefit from these improvements. As always, your feedback is very
welcome.

PRS

• [Doc] add load_data_using_stream_load.md @yandongxiao (#296)
• [Doc] update change_root_password_howto.md @yandongxiao (#295)
• [Bugfix] set proxy_pass_request_body off when redirect to FE @yandongxiao (#303)
• [Documentation] update automatic_scaling_for_cn_nodes_howto.md @yandongxiao (#299)
• [Chore] Add Github Actions to add label on issue and PR @yandongxiao (#297)

v1.8.5 🌈

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

1. [Chart] Service Account Customization: The operator now supports to provide the ability to add custom
   annotations and labels. The previous operator.global.rbac.serviceAccountName field is no longer supported.
2. [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

1. Fixed an issue that occurred when starrocks.initPassword.enabled is true and the value
   of starrocks.starrocksCluster.name is set. The FE service domain name would follow the set value, while the initpwd
   pod would still use the starrocks.nameOverride value 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)

v1.8.4 🌈

Release Notes for starrocks-kubernetes-operator v1.8.4

We are excited to announce the release of starrocks-kubernetes-operator v1.8.4, a Kubernetes operator for StarRocks.
This release brings several new features, bug fixes, and documentation improvements.

What's New

1. [Feature] add golangci-lint GitHub Action: This feature enables the golangci-lint tool to check the code quality
   and style of the operator project on every pull request.
2. [Feature] allow you to configure the terminationGracePeriodSeconds in StarRocksCluster CRD: This feature allows
   you to specify how long to wait before forcefully terminating a pod when deleting or updating a StarRocksCluster
   resource.
3. [Feature] add storage fields for starrocksCnSpec in values.yaml: This feature allows you to configure the storage
   class and size for the CN nodes in the StarRocksCluster.
4. [Feature] integration with Prometheus by ServiceMonitor CRD: This feature allows you to monitor the metrics of
   StarRocks cluster by using Prometheus and ServiceMonitor CRD.
5. [Feature] support startupProbeFailureSeconds fields in StarRocksCluster CRD: This feature allows you to configure
   the startup probe failure threshold for the pods in the StarRocksCluster resource.
6. [Feature] facilitate the configuration of environmental variables for the operator pod: for instance, one may
   designate KUBE_STARROCKS_UNSUPPORTED_ENVS to eliminate environments incompatible with the kubernetes cluster.

Bug Fixes

1. [Bugfix] This bugfix solves the problem that FE Proxy cannot handle stream load requests correctly when there are
   multiple FE pods in the StarRocks cluster.

Maintenance

1. [Doc] Set up StarRocks locally: This document provides a guide on how to set up a local StarRocks cluster.
2. [Doc] Establish a comprehensive StarRocks cluster, encompassing all available features. For additional examples
   concerning StarRocksCluster,
   please refer to: https://github.com/StarRocks/starrocks-kubernetes-operator/tree/main/examples/starrocks.
3. [Doc] Augment the instructional material on StarRocks utilization, encompassing topics such as '
   logging_and_related_configurations_howto.md' and 'mount_external_configmaps_or_secrets_howto.md'.
   For a holistic view of available guides,
   please refer to: https://github.com/StarRocks/starrocks-kubernetes-operator/tree/main/doc

Changes

🚀 Features

• [Feature] add golangci-lint Action @yandongxiao (#285)
• [Feature] allow to config the terminationGracePeriodSeconds @yandongxiao (#283)
• [Feature] add storage spec fields for starrocks cn spec in values.yaml @yandongxiao (#280)
• [Feature] integration with prometheus @yandongxiao (#284)
• [Feature] support customize probe @yandongxiao (#271)

🐛 Bug Fixes

• [Bugfix] fe proxy failed in multiple fe pods @yandongxiao (#269)
• [Bugfix] support k8s env which has no status.hostIP field @dujl (#266)

🧰 Maintenance

• [Doc] change related fields to release v1.8.4 @yandongxiao (#286)
• [Docs] install starrocks locally @yandongxiao (#274)
• [Doc] update examples/starrocks/deploy_a_starrocks_cluster_with_all_f… @yandongxiao (#278)
• [Doc] update doc/mount_external_configmaps_or_secrets_howto.md @yandongxiao (#277)
• [Docs] add starrocks-fe-and-be.yaml @yandongxiao (#276)
• [Doc] StarRocks Logging and Related Configurations @yandongxiao (#267)
• [Doc] Update deploy_a_starrocks_cluster_with_share_data_mode.yaml @DanRoscigno (#273)
• [Refactor] rename some name in pkg/k8sutils/templates/pod/spec.go @yandongxiao (#272)
• [Doc] add examples for StarRocksCluster CRD @yandongxiao (#270)
• [Doc] update comments in values.yaml @yandongxiao (#265)

v1.8.3 🌈

This is a minor release of StarRocks Kubernetes Operator.

What's New

1. [operator] Set proxy_read_timeout 600s: We have set proxy_read_timeout to 600s in nginx.conf, because the default value is 60s, which may cause timeout.
2. [chart] Add JAVA_OPTS_FOR_JDK_11 in FE config: We have added JAVA_OPTS_FOR_JDK_11 in FE config, because the default value is not suitable for JDK 11. If you used the default config of FE in values.yaml, Upgrading to v1.8.3 will cause the pods of FE to restart.
3. [chart] Allow user to specify serviceAccount for operator: By default the operator chart will create a serviceAccount for the operator, named starrocks. But if you want to use an existing serviceAccount, you can specify it in values.yaml.
4. [operator] Support Ports for feProxy component: We have supported Ports for feProxy component, allowing users to specify the nodePort of feProxy service.
5. [operator] Add namespace flag: It makes operator watch resources in a single namespace instead of all namespaces in the cluster. In most cases, you should not set this value. If your kubernetes cluster manages too many nodes, and operator watching all namespaces use too many memory resources, you can set this value.

Changes

• change related docs to release v1.8.3 @yandongxiao (#264)
• [Bugfix] change set proxy_read_timeout in nginx.conf @yandongxiao (#259)
• [Docs] Add JAVA_OPTS_FOR_JDK_11 to values.yaml @yandongxiao (#257)

🚀 Features

• add namespace flag to make operator watch resources in a single namespace @yandongxiao (#261)
• allow user to specify serviceAccount for operator @yandongxiao (#262)
• [Feature] Support nodePort for feProxy component @yandongxiao (#258)