[Chore] Prepare for v1.9.8 (#583)

* [Chore] Prepare for v1.9.8

Signed-off-by: yandongxiao <[email protected]>

* [Chore] change starrocks version

Signed-off-by: yandongxiao <[email protected]>

---------

Signed-off-by: yandongxiao <[email protected]>

Author: yandongxiao

CHANGELOG.md

@@ -1,5 +1,29 @@
 # CHANGELOG
 
+## [v1.9.8](https://github.com/StarRocks/starrocks-kubernetes-operator/releases/tag/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](https://github.com/StarRocks/starrocks-kubernetes-operator/pull/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](https://github.com/StarRocks/starrocks-kubernetes-operator/pull/579).
+3. [Helm Chart] Support config override.
+   [#580](https://github.com/StarRocks/starrocks-kubernetes-operator/pull/580).
+4. [Operator] Add update permission for starrocksclusters/finalizers resource for OpenShift.
+   [#484](https://github.com/StarRocks/starrocks-kubernetes-operator/pull/484)
+5. [Operator] Support to disable probe.
+   [#569](https://github.com/StarRocks/starrocks-kubernetes-operator/pull/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](https://github.com/StarRocks/starrocks-kubernetes-operator/releases/tag/v1.9.7)
 
 Release Notes for starrocks-kubernetes-operator v1.9.7

config/crd/bases/starrocks.com_starrocksclusters.yaml

@@ -4,7 +4,7 @@ kind: CustomResourceDefinition
 metadata:
   annotations:
     controller-gen.kubebuilder.io/version: v0.14.0
-    version: v1.9.7
+    version: v1.9.8
   name: starrocksclusters.starrocks.com
 spec:
   group: starrocks.com

config/crd/bases/starrocks.com_starrockswarehouses.yaml

@@ -4,7 +4,7 @@ kind: CustomResourceDefinition
 metadata:
   annotations:
     controller-gen.kubebuilder.io/version: v0.14.0
-    version: v1.9.7
+    version: v1.9.8
   name: starrockswarehouses.starrocks.com
 spec:
   group: starrocks.com

deploy/operator.yaml

@@ -168,7 +168,7 @@ spec:
         kubectl.kubernetes.io/default-container: manager
       labels:
         app: kube-starrocks-operator
-        version: 1.9.7
+        version: 1.9.8
     spec:
       automountServiceAccountToken: true
       containers:
@@ -181,7 +181,7 @@ spec:
         env:
         - name: TZ
           value: Asia/Shanghai
-        image: "starrocks/operator:v1.9.7"
+        image: "starrocks/operator:v1.9.8"
         imagePullPolicy: Always
         name: manager
         securityContext:

deploy/starrocks.com_starrocksclusters.yaml

@@ -4,7 +4,7 @@ kind: CustomResourceDefinition
 metadata:
   annotations:
     controller-gen.kubebuilder.io/version: v0.14.0
-    version: v1.9.7
+    version: v1.9.8
   name: starrocksclusters.starrocks.com
 spec:
   group: starrocks.com

deploy/starrocks.com_starrockswarehouses.yaml

@@ -4,7 +4,7 @@ kind: CustomResourceDefinition
 metadata:
   annotations:
     controller-gen.kubebuilder.io/version: v0.14.0
-    version: v1.9.7
+    version: v1.9.8
   name: starrockswarehouses.starrocks.com
 spec:
   group: starrocks.com

doc/api.md

@@ -1677,7 +1677,8 @@ Default failureThreshold is 60 and the periodSeconds is 5, this means the startu
 will fail if the pod can’t start in 300 seconds. Your StartupProbeFailureSeconds is
 the total time of seconds before startupProbe give up and fail the container start.
 If startupProbeFailureSeconds can’t be divided by defaultPeriodSeconds, the failureThreshold
-will be rounded up.</p>
+will be rounded up.
+Note: you can set it to 0 to disable the startup probe.</p>
 </td>
 </tr>
 <tr>
@@ -1693,7 +1694,8 @@ int32
 Default failureThreshold is 3 and the periodSeconds is 5, this means the liveness
 will fail if the pod can&rsquo;t respond in 15 seconds. Your LivenessProbeFailureSeconds is
 the total time of seconds before the container restart. If LivenessProbeFailureSeconds
-can&rsquo;t be divided by defaultPeriodSeconds, the failureThreshold will be rounded up.</p>
+can&rsquo;t be divided by defaultPeriodSeconds, the failureThreshold will be rounded up.
+Note: you can set it to 0 to disable the liveness probe.</p>
 </td>
 </tr>
 <tr>
@@ -1709,7 +1711,8 @@ int32
 Default failureThreshold is 3 and the periodSeconds is 5, this means the readiness
 will fail if the pod can&rsquo;t respond in 15 seconds. Your ReadinessProbeFailureSeconds is
 the total time of seconds before pods becomes not ready. If ReadinessProbeFailureSeconds
-can&rsquo;t be divided by defaultPeriodSeconds, the failureThreshold will be rounded up.</p>
+can&rsquo;t be divided by defaultPeriodSeconds, the failureThreshold will be rounded up.
+Note: you can set it to 0 to disable the readiness probe.</p>
 </td>
 </tr>
 <tr>
@@ -2273,5 +2276,5 @@ AutoScalingPolicy
 <hr/>
 <p><em>
 Generated with <code>gen-crd-api-reference-docs</code>
-on git commit <code>35451e5</code>.
+on git commit <code>354d3f8</code>.
 </em></p>

doc/automatic_scaling_for_cn_nodes_howto.md

@@ -91,7 +91,7 @@ Add the following snippets to `values.yaml` to configure the automatic scaling p
   starrocksCnSpec:
     image:
       repository: starrocks/cn-ubuntu
-      tag: 3.2-latest
+      tag: 3.3-latest
     resources:
       requests:
         cpu: 4

doc/build_your_own_container_image_howto.md

@@ -50,8 +50,8 @@ of [this PR](https://github.com/StarRocks/starrocks-kubernetes-operator/pull/288
 # clone the repository
 git clone https://github.com/StarRocks/starrocks-kubernetes-operator.git
 
-# checkout the latest released version, e.g., v1.9.7
-git checkout v1.9.7
+# checkout the latest released version, e.g., v1.9.8
+git checkout v1.9.8
 
 # revert the commit
 git revert 66e2f2c
@@ -78,9 +78,9 @@ make generate
 
 ```bash
 # replace the image name with your own, e.g. replace meaglekey to the username of the Docker Hub account
-docker build -t meaglekey/operator:v1.9.7-remove-appProtocol .
+docker build -t meaglekey/operator:v1.9.8-remove-appProtocol .
 
 # push the image to the Docker Hub
 # Note: you have to log in to the Docker Hub by `docker login` First.
-docker push meaglekey/operator:v1.9.7-remove-appProtocol
+docker push meaglekey/operator:v1.9.8-remove-appProtocol
 ```

doc/integration/integration-prometheus-grafana.md

@@ -111,7 +111,7 @@ spec:
     configMapInfo:
       configMapName: kube-starrocks-be-cm
       resolveKey: be.conf
-    image: starrocks/be-ubuntu:3.2-latest
+    image: starrocks/be-ubuntu:3.3-latest
     limits:
       cpu: 4
       memory: 4Gi
@@ -128,7 +128,7 @@ spec:
     configMapInfo:
       configMapName: kube-starrocks-fe-cm
       resolveKey: fe.conf
-    image: starrocks/fe-ubuntu:3.2-latest
+    image: starrocks/fe-ubuntu:3.3-latest
     limits:
       cpu: 4
       memory: 4Gi

doc/mount_persistent_volume_howto.md

@@ -28,7 +28,7 @@ metadata:
     cluster: kube-starrocks
 spec:
   starRocksFeSpec:
-    image: "starrocks/fe-ubuntu:3.2-latest"
+    image: "starrocks/fe-ubuntu:3.3-latest"
     replicas: 1
     storageVolumes:
     - name: fe-storage-meta
@@ -41,7 +41,7 @@ spec:
       storageSize: 5Gi
       mountPath: /opt/starrocks/fe/log
   starRocksBeSpec:
-    image: "starrocks/be-ubuntu:3.2-latest"
+    image: "starrocks/be-ubuntu:3.3-latest"
     replicas: 3
     storageVolumes:
     - name: be-storage-data
@@ -107,7 +107,7 @@ starrocks:
    starrocksFESpec:
       image:
          repository: starrocks/fe-ubuntu
-         tag: 3.2-latest
+         tag: 3.3-latest
       storageSpec:
          name: fe-storage
          storageClassName: standard-rwo   # standard-rwo is the default storageClassName in GKE.
@@ -116,7 +116,7 @@ starrocks:
    starrocksBeSpec:
       image:
          repository: starrocks/be-ubuntu
-         tag: 3.2-latest
+         tag: 3.3-latest
       replicas: 3
       storageSpec:
          name: be-storage

examples/starrocks/deploy_a_starrocks_cluster_with_be_capabilities.yaml

@@ -9,7 +9,7 @@ metadata:
     app.kubernetes.io/managed-by: Helm
 spec:
   starRocksFeSpec:
-    image: "starrocks/fe-ubuntu:3.2-latest"
+    image: "starrocks/fe-ubuntu:3.3-latest"
     replicas: 1
     limits:
       cpu: 8
@@ -30,7 +30,7 @@ spec:
       configMapName: kube-starrocks-fe-cm
       resolveKey: fe.conf
   starRocksBeSpec:
-    image: "starrocks/be-ubuntu:3.2-latest"
+    image: "starrocks/be-ubuntu:3.3-latest"
     replicas: 1
     limits:
       cpu: 8

helm-charts/charts/kube-starrocks/Chart.yaml

@@ -25,13 +25,13 @@ maintainers:
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 1.9.7
+version: 1.9.8
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: 3.2-latest
+appVersion: 3.3-latest
 
 kubeVersion: ">=1.18.3-0"
 
@@ -43,10 +43,10 @@ keywords:
 
 dependencies:
   - name: operator
-    version: 1.9.7
+    version: 1.9.8
     repository: "file://charts/operator"
   - name: starrocks
-    version: 1.9.7
+    version: 1.9.8
     repository: "file://charts/starrocks"
 
 sources:

helm-charts/charts/kube-starrocks/charts/operator/Chart.yaml

@@ -25,13 +25,13 @@ maintainers:
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 1.9.7
+version: 1.9.8
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: 1.9.7
+appVersion: 1.9.8
 
 kubeVersion: ">=1.18.3-0"
 

helm-charts/charts/kube-starrocks/charts/operator/values.yaml

@@ -36,7 +36,7 @@ starrocksOperator:
   image:
     # image sliced by "repository:tag"
     repository: starrocks/operator
-    tag: v1.9.7
+    tag: v1.9.8
   imagePullPolicy: Always
   replicaCount: 1
   resources:

helm-charts/charts/kube-starrocks/charts/starrocks/Chart.yaml

@@ -25,13 +25,13 @@ maintainers:
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 1.9.7
+version: 1.9.8
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: 3.2-latest
+appVersion: 3.3-latest
 
 kubeVersion: ">=1.18.3-0"
 

helm-charts/charts/kube-starrocks/charts/starrocks/values.yaml

@@ -77,7 +77,7 @@ starrocksCluster:
   #   2. the values in their own spec will replace all the values in this field, not merge.
   componentValues:
     image:
-      tag: "3.2-latest"
+      tag: "3.3-latest"
     # hostAliases allows adding entries to /etc/hosts inside the containers.
     hostAliases: []
       # - ip: "127.0.0.1"

helm-charts/charts/kube-starrocks/values.yaml

@@ -43,7 +43,7 @@ operator:
     image:
       # image sliced by "repository:tag"
       repository: starrocks/operator
-      tag: v1.9.7
+      tag: v1.9.8
     imagePullPolicy: Always
     replicaCount: 1
     resources:
@@ -185,7 +185,7 @@ starrocks:
     #   2. the values in their own spec will replace all the values in this field, not merge.
     componentValues:
       image:
-        tag: "3.2-latest"
+        tag: "3.3-latest"
       # hostAliases allows adding entries to /etc/hosts inside the containers.
       hostAliases: []
         # - ip: "127.0.0.1"

helm-charts/charts/warehouse/Chart.yaml

@@ -23,13 +23,13 @@ maintainers:
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 1.9.7
+version: 1.9.8
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: 3.2-latest
+appVersion: 3.3-latest
 
 kubeVersion: ">=1.18.3-0"
 

helm-charts/charts/warehouse/values.yaml

@@ -35,7 +35,7 @@ spec:
     # image sliced by "repository:tag"
     repository: starrocks/cn-ubuntu
     # Note: the image tag must be greater than or equal to 3.2.0
-    tag: 3.2-latest
+    tag: 3.3-latest
   # serviceAccount for pod access cloud service.
   serviceAccount: ""
   # add annotations for pods. example, if you want to config monitor for datadog, you can config the annotations.