How to specify the image in `starrocks` cluster CR...
# questions-and-troubleshooting
s
How to specify the image in
starrocks
cluster CRD ?
Copy code
componentValues:
    image:
      tag: "3.5-latest"
We typically have our production pull images from a caching artifactory internal repository
For the operator itself, I was able to do it:
Copy code
image:
    # image sliced by "repository:tag"
    repository: our-artifactory-host.tools/docker-public-cache/starrocks/operator
    tag: v1.11.4
Basically we need to add a static prefix to all images
@Rocky can you help ?
r
Hello! I'm Rocky, your StarRocks assistant. I'd be happy to help you! What are you working on? If you have a specific question about a query, an error message you're seeing, or how to use a particular StarRocks feature, just let me know and I'll do my best to provide the information you need.
s
Set a static prefix for all docker image templated by the starrocks crd
p
This is about configuring custom image repositories in the StarRocks Kubernetes Operator CRD — specifically adding a static prefix (like an internal Artifactory cache) to all container images. For the operator itself, Simon already found the solution with the
image.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:
Copy code
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:
Copy code
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.
🙌 1
s
Thanks Peter