Add chsrt starrocks 1.11.3

charts/starrocks/BUILD-README.md

@@ -9,7 +9,7 @@ $ git clone https://github.com/paasup/dip-catalog.git
 
 - 작업 브랜치로 체크아웃
 ```
-$ git checkout -b update-starrocks/1.11.0
+$ git checkout -b update-starrocks/1.11.3
 ```
 
 ## 2. 차트 갱신
@@ -38,7 +38,7 @@ $ git checkout -b update-starrocks/1.11.0
   helm search repo starrocks/starrocks
   
   # helm 차트 다운로드
-  helm pull starrocks/starrocks --version=1.11.0
+  helm pull starrocks/starrocks --version=1.11.3
   
   # 차트 압축 해제
   tar xzvf starrocks-*.tgz
@@ -51,22 +51,22 @@ $ git checkout -b update-starrocks/1.11.0
 - 갱신작업 진행후 commit
 ```
 $ git add .
-$ git commit -m "update-starrocks/1.11.0"
+$ git commit -m "update-starrocks/1.11.3"
 ```
 
 - main 브랜치에 체크아웃 후 merge
 ```
 $ git checkout main
-$ git merge update-starrocks/1.11.0
+$ git merge update-starrocks/1.11.3
 ```
 
 - git에 push 후 작업 브랜치 삭제
 ```
 $ git push -u origin main
-$ git branch -d update-starrocks/1.11.0
+$ git branch -d update-starrocks/1.11.3
 ```
 
 - git tag 추가 후 push
 ```
-$ git tag starrocks/1.11.0
+$ git tag starrocks/1.11.3
-$ git push origin starrocks/1.11.0
+$ git push origin starrocks/1.11.3

charts/starrocks/Chart.yaml

@@ -20,4 +20,4 @@ name: starrocks
 sources:
 - https://github.com/StarRocks/starrocks
 type: application
-version: 1.11.0
+version: 1.11.3

charts/starrocks/templates/_helpers.tpl

@@ -618,6 +618,8 @@ Get the value of the runAsNonRoot field in the starrocksFESpec
 {{- .Values.starrocksFESpec.runAsNonRoot -}}
 {{- else if .Values.starrocksCluster.componentValues.runAsNonRoot -}}
 {{- .Values.starrocksCluster.componentValues.runAsNonRoot -}}
+{{- else -}}
+false
 {{- end -}}
 {{- end -}}
 
@@ -629,6 +631,8 @@ Get the value of the runAsNonRoot field in the starrocksBeSpec
 {{- .Values.starrocksBeSpec.runAsNonRoot -}}
 {{- else if .Values.starrocksCluster.componentValues.runAsNonRoot -}}
 {{- .Values.starrocksCluster.componentValues.runAsNonRoot -}}
+{{- else -}}
+false
 {{- end -}}
 {{- end -}}
 
@@ -640,6 +644,8 @@ Get the value of the runAsNonRoot field in the starrocksCnSpec
 {{- .Values.starrocksCnSpec.runAsNonRoot -}}
 {{- else if .Values.starrocksCluster.componentValues.runAsNonRoot -}}
 {{- .Values.starrocksCluster.componentValues.runAsNonRoot -}}
+{{- else -}}
+false
 {{- end -}}
 {{- end -}}
 

charts/starrocks/templates/starrockscluster.yaml

@@ -201,6 +201,8 @@ spec:
     {{- if .Values.starrocksFESpec.readinessProbeFailureSeconds }}
     readinessProbeFailureSeconds: {{ .Values.starrocksFESpec.readinessProbeFailureSeconds }}
     {{- end }}
+    minReadySeconds: {{ .Values.starrocksFESpec.minReadySeconds }}
+    podManagementPolicy: {{ .Values.starrocksFESpec.podManagementPolicy }}
     {{- if .Values.starrocksFESpec.lifecycle }}
     lifecycle:
       {{- toYaml .Values.starrocksFESpec.lifecycle | nindent 6 }}
@@ -478,6 +480,8 @@ spec:
     {{- if .Values.starrocksBeSpec.readinessProbeFailureSeconds }}
     readinessProbeFailureSeconds: {{ .Values.starrocksBeSpec.readinessProbeFailureSeconds }}
     {{- end }}
+    minReadySeconds: {{ .Values.starrocksBeSpec.minReadySeconds }}
+    podManagementPolicy: {{ .Values.starrocksBeSpec.podManagementPolicy }}
     {{- if .Values.starrocksBeSpec.lifecycle }}
     lifecycle:
       {{- toYaml .Values.starrocksBeSpec.lifecycle | nindent 6 }}
@@ -723,6 +727,8 @@ spec:
     {{- if .Values.starrocksCnSpec.readinessProbeFailureSeconds }}
     readinessProbeFailureSeconds: {{ .Values.starrocksCnSpec.readinessProbeFailureSeconds }}
     {{- end }}
+    minReadySeconds: {{ .Values.starrocksCnSpec.minReadySeconds }}
+    podManagementPolicy: {{ .Values.starrocksCnSpec.podManagementPolicy }}
     {{- if .Values.starrocksCnSpec.lifecycle }}
     lifecycle:
       {{- toYaml .Values.starrocksCnSpec.lifecycle | nindent 6 }}

charts/starrocks/values.yaml

@@ -445,6 +445,19 @@ starrocksFESpec:
   # the default value is 15 seconds
   # You can set it to "0" to disable the probe.
   readinessProbeFailureSeconds:
+  # minReadySeconds specifies the minimum number of seconds for which a newly created pod should be ready
+  # without any of its container crashing, for it to be considered available.
+  # Defaults to 0 (pod will be considered available as soon as it is ready).
+  # see https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#minimum-ready-seconds for more details.
+  # Note: If you want to this field take effect, you need set podManagementPolicy to OrderedReady.
+  minReadySeconds: 0
+  # podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down.
+  # The default policy is Parallel which is not the same as statefulset's default policy. The reason is that we previously hoped
+  # to execute scale-out and scale-in parallel, which is safe for CN, but does pose data security issues for BE.
+  # Note: If you have changed this field, then the related statefulset object need to be recreated, or there will be an error like this:
+  #       updates to statefulset spec for fields other than 'replicas', 'ordinals', 'template', 'updateStrategy',
+  #       'persistentVolumeClaimRetentionPolicy' and 'minReadySeconds' are forbidden
+  podManagementPolicy: Parallel
   # Lifecycle describes actions that the management system should take in response to container lifecycle events.
   # By default, Operator will add corresponding preStop hooks for different components. For example, the preStop
   # script for the FE Component is /opt/starrocks/fe_prestop.sh, for the BE Component is /opt/starrocks/be_prestop.sh,
@@ -798,6 +811,19 @@ starrocksCnSpec:
   # the default value is 15 seconds
   # You can set it to "0" to disable the probe.
   readinessProbeFailureSeconds:
+  # minReadySeconds specifies the minimum number of seconds for which a newly created pod should be ready
+  # without any of its container crashing, for it to be considered available.
+  # Defaults to 0 (pod will be considered available as soon as it is ready).
+  # see https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#minimum-ready-seconds for more details.
+  # Note: If you want to this field take effect, you need set podManagementPolicy to OrderedReady.
+  minReadySeconds: 0
+  # podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down.
+  # The default policy is Parallel which is not the same as statefulset's default policy. The reason is that we previously hoped
+  # to execute scale-out and scale-in parallel, which is safe for CN, but does pose data security issues for BE.
+  # Note: If you have changed this field, then the related statefulset object need to be recreated, or there will be an error like this:
+  #       updates to statefulset spec for fields other than 'replicas', 'ordinals', 'template', 'updateStrategy',
+  #       'persistentVolumeClaimRetentionPolicy' and 'minReadySeconds' are forbidden
+  podManagementPolicy: Parallel
   # Lifecycle describes actions that the management system should take in response to container lifecycle events.
   # By default, Operator will add corresponding preStop hooks for different components. For example, the preStop
   # script for the FE Component is /opt/starrocks/fe_prestop.sh, for the BE Component is /opt/starrocks/be_prestop.sh,
@@ -1117,6 +1143,19 @@ starrocksBeSpec:
   # the default value is 15 seconds
   # You can set it to "0" to disable the probe.
   readinessProbeFailureSeconds:
+  # minReadySeconds specifies the minimum number of seconds for which a newly created pod should be ready
+  # without any of its container crashing, for it to be considered available.
+  # Defaults to 0 (pod will be considered available as soon as it is ready).
+  # see https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#minimum-ready-seconds for more details.
+  # Note: If you want to this field take effect, you need set podManagementPolicy to OrderedReady.
+  minReadySeconds: 0
+  # podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down.
+  # The default policy is Parallel which is not the same as statefulset's default policy. The reason is that we previously hoped
+  # to execute scale-out and scale-in parallel, which is safe for CN, but does pose data security issues for BE.
+  # Note: If you have changed this field, then the related statefulset object need to be recreated, or there will be an error like this:
+  #       updates to statefulset spec for fields other than 'replicas', 'ordinals', 'template', 'updateStrategy',
+  #       'persistentVolumeClaimRetentionPolicy' and 'minReadySeconds' are forbidden
+  podManagementPolicy: Parallel
   # Lifecycle describes actions that the management system should take in response to container lifecycle events.
   # By default, Operator will add corresponding preStop hooks for different components. For example, the preStop
   # script for the FE Component is /opt/starrocks/fe_prestop.sh, for the BE Component is /opt/starrocks/be_prestop.sh,