Project: StarRocks (App Definition and Development / Database)
File: starrocks-kubernetes-operator.md

displayed_sidebar: "English" The Operator provided by StarRocks is used to deploy StarRocks clusters in the Kubernetes environment. The StarRocks cluster components include FE, BE, and CN. User guide: You can use the following methods to deploy StarRocks clusters on Kubernetes: Source codes: Download URL of the resources: URL prefix `https://github.com/StarRocks/starrocks-kubernetes-operator/releases/download/v${operatorversion}/${resourcename}` Resource name StarRocksCluster CRD: `starrocks.com_starrocksclusters.yaml` Default configuration file for StarRocks Operator: `operator.yaml` Helm Chart, including `kube-starrocks` Chart `kube-starrocks-${chartversion}.tgz`. The `kube-starrocks` Chart is divided into two subcharts: `starrocks` Chart `starrocks-${chartversion}.tgz` and `operator` Chart `operator-${chart_version}.tgz`. For example, the download URL for kube-starrocks chart v1.8.6 is: `https://github.com/StarRocks/starrocks-kubernetes-operator/releases/download/v1.8.6/kube-starrocks-1.8.6.tgz` Version requirements Kubernetes: 1.18 or later Go: 1.19 or later Improvements Bug Fixes Fixed the following issues: New features Add StarRocksWarehouse CRD to support StarRocks Warehouse. Note that StarRocks Warehouse is currently a feature of the StarRocks Enterprise Edition. Enhancements Add the `status.reason` field in StarRocksCluster CRD. When the apply operation of a subcontroller fails during cluster deployment, you can execute `kubectl get starrockscluster <nameofthestarrockscluster_object> -oyaml`, and view error logs shown in `status.reason` field in the returned result. An empty directory can be mounted in the `storageVolumes` field. Bug Fixes Fixed the following issues: The status of the StarRocks cluster was inconsistent with the status of the cluster's FE, BE and CN components. The HPA resource is not deleted when `autoScalingPolicy` is deleted. The HPA resource is not removed when `starRocksCnSpec` is deleted. Bugfixes Enhancements Add the `livenessProbeFailureSeconds` and `readinessProbeFailureSeconds` fields in StarRocksCluster CRD. When StarRocks is under heavy workload and the time of liveness and readiness probes still use default values, the liveness and readiness probes may fail and cause the containers to restart. In this case, you can add larger values to these two fields. Bug Fixes Fixed the following issue: An error `sendfile() failed (32: Broken pipe) while sending request to upstream` is returned during a Stream Load job. After Nginx sends the request body to FE, the FE then redirects the request to the BE. At this point, the data cached in Nginx may already be lost. Doc Improvements Bug Fixes Fixed the following issue: ) Upgrade notes [Helm Chart] When the value specified in `starrocks.starrocksCluster.name` is different from the value of `starrocks.nameOverride`, the old configmaps for FE, BE, and CN will be deleted. New configmaps with new names for the FE, BE, and CN will be created. This may result in the restart of the FE, BE, and CN pods. Features . Add the `terminationGracePeriodSeconds` in the StarRocksCluster CRD to configure how long to wait before forcefully terminating a pod when a StarRocksCluster resource is being deleted or

Add the `startupProbeFailureSeconds` field in the StarRocksCluster CRD to configure the startup probe failure threshold for the pods in the StarRocksCluster resource. Bug Fixes Fixed the following issue: The FE Proxy cannot handle STREAM LOAD requests correctly when multiple FE pods exist in the StarRocks cluster. Doc . Add more user guides on how to deploy a StarRocks cluster with different configurations. For example, how to . For more user guides, see . Add more user guides on how to manage the StarRocks cluster. For example, how to configure and . For more user guides, see . Upgrade notes Features Improvements The value of the `proxyreadtimeout` parameter is changed in the nginx.conf file to 600s from 60s, in order to avoid timeout. Improvements Increase the maximum memory usage allowed for the operator pods to avoid OOM. Features Support using , allowing users to mount specific files or directories from these resources. Add the `ports` field in the StarRocks cluster CRD to allow users to customize the ports of the services. Improvements Remove the related Kubernetes resources when the `BeSpec` or `CnSpec` of the StarRocks cluster is deleted, ensuring a clean and consistent state of the cluster. Upgrade notes and behavior changes [Operator] To upgrade the StarRocksCluster CRD and operator you need to manually apply the new StarRocksCluster CRD starrocks.com_starrocksclusters.yaml and operator.yaml. [Helm Chart] To upgrade the Helm Chart, you need to perform the following: Use the values migration tool to adjust the format of the previous values.yaml file to the new format. The values migration tool for different operating systems can be downloaded from the section. You can get help information of this tool by running the `migrate-chart-value --help` command. ```Bash migrate-chart-value --input values.yaml --target-version v1.8.0 --output ./values-v1.8.0.yaml ``` Update the Helm Chart repo. ```Bash helm repo update ``` Execute the `helm upgrade` command to apply the adjusted values.yaml file to the StarRocks helm chart kube-starrocks. ```Bash helm upgrade <release-name> starrocks-community/kube-starrocks -f values-v1.8.0.yaml ``` Two subcharts, and , are added into the kube-starrocks helm chart. You can choose to install StarRocks operator or StarRocks cluster respectively by specifying the corresponding subchart. This way, you can manage StarRocks clusters more flexibly, such as deploying one StarRocks operator and multiple StarRocks clusters. Features when executing the `helm install` command. Note that, the `helm upgrade` command does not support this feature. . Improvements Add the `subpath` field in StarRocksCluster CRD. Increase the disk size allowed for the FE metadata. The FE container stops running when the available disk space that can be provisioned to store the FE metadata is less than that default value.