v1.9.8 🌈

Release Notes for starrocks-kubernetes-operator v1.9.8

We are excited to announce the release of StarRocks Kubernetes Operator v1.9.8. This version has the following
enhancements:

1. [Helm Chart] Support multiple data volumes on helm chart. #578.
2. [Helm Chart] Use a reasonable volume size for logging for BE/CN. Because the logStorageSize field of the Helm Chart
   is modified. If the user uses the default value, the Operator will try to update the PVC part of the component's
   Statefulset. Statefulset does not allow this part of the configuration to be updated, so there is a case of tuning
   failure. The solution is to set it to the original default value, 1GB. #579.
3. [Helm Chart] Support config override. #580.
4. [Operator] Add update permission for starrocksclusters/finalizers resource for OpenShift. #484
5. [Operator] Support to disable probe. #569

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.7 🌈

Release Notes for starrocks-kubernetes-operator v1.9.7

We are excited to announce the release of StarRocks Kubernetes Operator v1.9.7. This version has the following
enhancements and bug fixes:

1. [Operator] Fix the problem that FE proxy will fail when FE external service is recreated #557.
2. [Operator] Add loadBalancerSourceRanges field to support setting the source IP range for the load balancer #551.
3. [Operator] Add topologySpreadConstraints field to support setting the topology spread constraints for pods #546.
4. [Operator] Add CRD version information to CRD annotations #544
5. [Operator] Make it easy to configure the hostPath volume #552
6. [Chart] Add spill storage volume for BE and CN #547
7. [Chart] Remove JAVA_OPTS_FOR_JDK_9 and JAVA_OPTS_FOR_JDK_11 env from fe config, this will cause the pods of FE to restart if you are using the default config of FE in values.yaml #542
8. [Documentation] We have added or updated some documents to help users deploy and manage StarRocks clusters on Kubernetes. #524 #525 #527 #530 #531 #532 #536 #538.

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.6 🌈

Release Notes for starrocks-kubernetes-operator v1.9.6

We are excited to announce the release of StarRocks Kubernetes Operator v1.9.6. This version has the following enhancements:

1. Support command and args(#516) in StarRocksCluster spec. You can easily customize the command and args if you are using helm chart.
   Below is a code snippet from values.yaml for your reference:

    entrypoint:
      script: |
        #! /bin/bash
        echo "do something before start cn"
        exec /opt/starrocks/cn_entrypoint.sh $FE_SERVICE_NAME

2. Support ImagePullPolicy in StarRocksCluster spec(#514).
3. Support to use namespaced scope permission to deploy warehouses(#513).

v1.9.5 🌈

Release Notes for starrocks-kubernetes-operator v1.9.5

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

Feature

• [Feature] Support init Containers. User can add a k8s pod format initContainers. PR #499 #508
• [Feature] Support sidecars. User can add a k8s pod format sidecars. PR #461
• [Feature] Support deploy multiple StarRocks clusters in one namespace. PR #493 #509

Enhancements

• [Enhancement] Support users to apply their own resources. PR #496
• [Enhancement] Support to customize securityContext for Operator Chart. PR #495
• [Enhancement] Support warehouse to be deployed in different namespace with StarRocks cluster. PR #505

Maintenance

[Chore] This PR aims to standardize the format of YAML files in templates directory. PR #501
[Chore] Upgrade Golang version to 1.22, and sigs.k8s.io/controller-runtime to v0.14.0. PR #497

v1.9.4 🌈

Release Notes for starrocks-kubernetes-operator v1.9.4

We are excited to announce the release of StarRocks Kubernetes Operator v1.9.4. 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] We've refined the logic for detecting Kubernetes versions, enhancing compatibility. PR #469
• [Operator] Operator: Added checks for volume name and mount path when a default emptyDir volume is incorporated. PR #464
• [Chart] Helm chart allows the exposure of the DataDog config.mode. PR #482

Bug Fixes

• [Operator] Addressed an issue by attempting to use a different version for deleting HPA (Horizontal Pod Autoscaler)
  again, aiming for a more reliable deletion process. PR #468
• [Chart] Make sure xx-config-hash is a valid string. PR #480
• [Chart] Introduced support for tolerations in the init-password job. PR #463

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.