Images

Overview

You can manage images using SWR or a third-party image repository. This section describes how images are pulled when the bursting add-on is installed in a CCE cluster.

• Pulling an Image from SWR on the Console
• Pulling an Image from a Third-Party Image Repository
• Using Both SWR and a Third-Party Image Repository

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.
  2. Create a workload on the CCE cluster console and select an image.

     

  3. The image will be pulled from SWR. Ensure that your image has been pushed to SWR. For details, see the SWR documentation.
• Method 2: Selecting an Image from SWR Using YAML
  1. Log in to the CCE cluster node.
  2. View the image address in SWR.

     Image address: swr.***.com/cci-test/nginx:1.0.0.x86_64_test

  3. Configure the YAML file of the workload.

     apiVersion: apps/v1
     kind: Deployment
     metadata:
       name: test
       namespace: default
       labels:
         virtual-kubelet.io/burst-to-cci: 'auto'    # Schedules the workload to CCI.
     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  dep.yaml

Pulling an Image from a Third-Party Image Repository

1. Use the tool provided by CCI to create a secret for authenticating the third-party image repository.

   imagepull-secret-generator --ak=$ak --sk=$sk --private-user=$user --private-password=$password --output-file-path=my-imagepull-secret.json --project-name=region --secret-name=my-imagepull-secret --swr-address=swr.***.com

   Log in to the CCE cluster node and create a secret for the cluster.

   kubectl apply -f my-imagepull-secret.json

2. Create a workload and specify the secret for authenticating the third-party image repository in spec.imagePullSecrets.

   Create a workload and specify the secret for authenticating the third-party image repository in spec.imagePullSecrets.

   apiVersion: apps/v1
   kind: Deployment
   metadata:
     labels:
       app: test-imagepull
       virtual-kubelet.io/burst-to-cci: enforce
     name: test-imagepull
   spec:
     replicas: 1
     selector:
       matchLabels:
         app: test-imagepull
     template:
       metadata:
         labels:
           app: test-imagepull
       spec:
         containers:
         - image: xxx/my-image:latest
           imagePullPolicy: Always
           name: nginx
           resources:
             limits:
               cpu: 1
               memory: 2Gi
             requests:
               cpu: 1
               memory: 2Gi
         imagePullSecrets:
         - name: my-imagepull-secret

Using Both SWR and a Third-Party Image Repository

Scenario

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 workloads scheduled to CCI use the image during traffic spikes. This speeds up image pull.