yandongxiao

``` persistentVolumeClaimRetentionPolicy describes the lifecycle of persistent volume claims created from volumeClaimTemplates. By default, all persistent volume claims are created as needed and retained until manually deleted. This policy allows...

‌‌‌If we are just marking the version information of CRD, can we add the corresponding version information to the annotation or label of CRD?

StarRocks(3.2) now does not support to run on ReadOnly file system. So we can not set `pod.spec.containers.securityContext.readOnlyRootFilesystem` to true. In order to run StarRocks on read-only file system, we can...

This should be a domain name resolution issue caused by accessing the SR deployed within k8s from outside the k8s cluster. There is currently no solution.

We will add a field preStartScriptLocation, and you can down load the binary before container process start. see https://github.com/StarRocks/starrocks-kubernetes-operator/pull/355

Please see https://github.com/StarRocks/starrocks-kubernetes-operator/blob/main/doc/load_data_using_stream_load_howto.md

This is a DNS Resolution issue, can you please give the network & DNS configuration in k8s?

If you are using coreDNS, https://github.com/coredns/coredns/issues/4297 and https://github.com/coredns/coredns/issues/4357 issues may help you. 1. one user said: I have upgraded our cluster to coredns:v1.7.0 and increased cpu resource 0.1 -> 0.5...

Two conclusions can be drawn from the FE Leader's logs: 1. Multiple threads are reporting SystemInfoService.getBackendWithBePort():556 at the same time. It is suspected that the JVM DNS Cache has expired,...

Has the BE's Pod ever experienced a restart ?