Help Center/ Cloud Container Instance (CCI)/ User Guide/ Using CCI with CCE/ Images
Updated on 2026-04-28 GMT+08:00
View PDF
Share

Images

You can manage images using SWR. This section describes how images are pulled when the CCE Cloud Bursting Engine for CCI add-on is installed in a CCE cluster.

Pulling an Image from SWR on the Console

  • Method 1: Selecting an Image from SWR on the CCE Console
    1. Upload an image to SWR. For details, see the SWR documentation.
    1. Click Select Image when creating a workload on the CCE cluster console.

    2. The image will be pulled from SWR. Ensure that the image has been uploaded to SWR. For details, see the SWR documentation.
  • Method 2: Selecting an Image from SWR by Configuring a Node in a CCE Cluster
    1. View the image path in the SWR image repository, for example, swr.cn-north-4.myhuaweicloud.com/cci-test/nginx:1.0.0.x86_64_test.

      cn-north-4 indicates the region, and cci-test is the SWR organization.

    2. Log in to a CCE cluster node.
    3. Configure the YAML file of the workload. 
      apiVersion: apps/v1
kind: Deployment
metadata:
  name: test
  namespace: default
  labels:
    bursting.cci.io/burst-to-cci: enforce    # The workload will be scheduled to CCI 2.0.
spec:
  replicas: 2
  selector:
    matchLabels:
      app: test
  template:
    metadata:
      labels:
        app: test
    spec:
      containers:
        - image: swr.***.com/cci-test/nginx:1.0.0.x86_64_test
          name: container-0
          resources:
            requests:
              cpu: 250m
              memory: 512Mi
            limits:
              cpu: 250m
              memory: 512Mi
          volumeMounts: []
      imagePullSecrets:
        - name: default-secret
    4. Deploy the workload. 
      kubectl apply -f  test-deployment.yaml

Pulling Images from Both SWR and a Third-Party Image Repository

Scenarios

In some cases, an image can be pulled from a third-party image repository when you create a workload on the CCE cluster console. The pulled image can be synchronized to SWR so that the workload scheduled to CCI can use the image during traffic spikes. This speeds up image pull.

Procedure

Configure annotations in the YAML file of the workload. The following is an example:

bursting.cci.io/image-replacement: '[
    {"repositoryPrefix":"harbor.domain","replaceWith":"swr.***.com/org1"},
    {"repositoryPrefix":"","replaceWith":"swr.***.com/org1"},
    {"repositoryPrefix":"harbor.domain/a/b/c/d","replaceWith":"swr.***.com/org2"}
]'
  • Replacement policies can be executed in any sequence.
  • Multiple replacement policies can be configured. The value of repositoryPrefix for each policy must be unique.
Table 1 Parameter description

Replacement Policy Key

Description

Remarks

repositoryPrefix

Image prefix that you want to match and replace
  • If this field is an empty string (""), all containers whose image values do not contain slashes (/) are matched.
  • If this field is not empty, all containers whose image values have the same prefix and end with slashes (/) are matched.
  • This field cannot end with a slash (/) and must be verified in the same way as the container image name.

replaceWith

Image prefix to be used
  • The value of this field cannot be the same as that of repositoryPrefix.
  • This field cannot end with a slash (/) and must be verified in the same way as the container image name.
Table 2 Annotations

Annotation

Before Replacement

After Replacement

Description

bursting.cci.io/image-replacement: '[

{"repositoryPrefix":"harbor.domain","replaceWith":"swr.***.com/org1"}

]'

containers:

- name: container-0

image: 'harbor.domain/ubuntu:latest'

containers:

- name: container-0

image: 'swr.***.com/org1/ubuntu:latest'

repositoryPrefix matches the domain name of a third-party repository.

bursting.cci.io/image-replacement: '[

{"repositoryPrefix":"","replaceWith":"swr.***.com/org1"}

]'

containers:

- name: container-1

image: 'nginx:latest'

containers:

- name: container-1

image: 'swr.***.com/org1/nginx:latest'

repositoryPrefix is an empty string.

bursting.cci.io/image-replacement: '[

{"repositoryPrefix":"harbor.domain/a/b/c/d","replaceWith":"swr.***.com/org2"}

]'

containers:

- name: container-2

image: 'harbor.domain/a/b/c/d/redis:latest'

containers:

- name: container-2

image: 'swr.***.com/org2/redis:latest'

repositoryPrefix matches the domain name of a third-party repository and the organization directory.
Parent Topic: Using CCI with CCE