Simon Paradis
04/01/2026, 7:23 PMstarrocks cluster CRD ?Simon Paradis
04/01/2026, 7:23 PMcomponentValues:
image:
tag: "3.5-latest"Simon Paradis
04/01/2026, 7:24 PMSimon Paradis
04/01/2026, 7:25 PMimage:
# image sliced by "repository:tag"
repository: our-artifactory-host.tools/docker-public-cache/starrocks/operator
tag: v1.11.4Simon Paradis
04/01/2026, 7:26 PMSimon Paradis
04/01/2026, 7:26 PMRocky
04/01/2026, 7:26 PMSimon Paradis
04/01/2026, 7:27 PMpeter pang
04/02/2026, 6:38 PMimage.repository and image.tag fields. The question is how to do the same for the StarRocks cluster components (FE, BE, CN).
In the StarRocksCluster CRD, you can specify the full image for each component individually rather than just using componentValues.image.tag. Here’s how:
apiVersion: starrocks.com/v1
kind: StarRocksCluster
metadata:
name: my-cluster
spec:
starRocksFeSpec:
image: our-artifactory-host.tools/docker-public-cache/starrocks/fe-ubuntu:3.5-latest
starRocksBeSpec:
image: our-artifactory-host.tools/docker-public-cache/starrocks/be-ubuntu:3.5-latest
starRocksCnSpec:
image: our-artifactory-host.tools/docker-public-cache/starrocks/cn-ubuntu:3.5-latest
Each component spec (starRocksFeSpec, starRocksBeSpec, starRocksCnSpec) has an image field that takes a full image reference including your custom registry prefix.
If Simon is using a Helm chart to deploy the cluster, the equivalent in values.yaml would be something like:
starrocksFESpec:
image:
repository: our-artifactory-host.tools/docker-public-cache/starrocks/fe-ubuntu
tag: "3.5-latest"
starrocksBeSpec:
image:
repository: our-artifactory-host.tools/docker-public-cache/starrocks/be-ubuntu
tag: "3.5-latest"
The key point is that unlike the operator (which has a single image block), the cluster CRD requires specifying the image per component since FE, BE, and CN use different base images. There isn’t a single “global prefix” setting — each component’s image needs to be set explicitly with the full Artifactory path.Simon Paradis
04/08/2026, 5:23 PM