Using Third-Party Images

Scenario

CCE allows you to create workloads using images pulled from third-party image repositories.

Generally, a third-party image repository can only be accessed after authentication (using your username and password). CCE uses the secret-based authentication to pull images. You need to create a secret for an image repository before pulling images from the repository.

Prerequisites

CCE Autopilot can access the network where the private repository is located. There are two options for this:

• Access over a private network: Ensure that the VPC of the private repository is the same as the VPC where the cluster resides.
• Access over Direct Connect or VPN: Connect the private repository network to the VPC where the cluster resides through Direct Connect or VPN.

Using the Console

1. Create a secret for accessing a third-party image repository.

   Click the cluster name to access the cluster console. In the navigation pane on the left, choose ConfigMaps and Secrets. On the Secrets tab, click Create Secret in the upper right corner. Set Secret Type to kubernetes.io/dockerconfigjson. For details, see Creating a Secret.

   Enter the username and password used to access the third-party image repository.

   Figure 1 Creating a secret
   

2. When creating a workload, you can enter a private image path (such as domainname/namespace/imagename:tag) in Image Name and select the key created in 1.
   Figure 2 Private image path
   

3. Set other parameters and click Create Workload.

Using kubectl

1. Use kubectl to connect to the cluster. For details, see Connecting to a Cluster Using kubectl.
2. Use kubectl to create a secret of the kubernetes.io/dockerconfigjson.

   kubectl create secret docker-registry myregistrykey  -n default --docker-server=DOCKER_REGISTRY_SERVER --docker-username=DOCKER_USER --docker-password=DOCKER_PASSWORD --docker-email=DOCKER_EMAIL

   In the preceding command, myregistrykey indicates the key name, default indicates the namespace where the key is located, and other parameters are as follows:

   • DOCKER_REGISTRY_SERVER: address of a third-party image repository, for example, www.3rdregistry.com or 10.10.10.10:443
   • DOCKER_USER: account used for logging in to a third-party image repository
   • DOCKER_PASSWORD: password used for logging in to a third-party image repository
   • DOCKER_EMAIL: email of a third-party image repository

3. Use a third-party image to create a workload.
   A kubernetes.io/dockerconfigjson secret is used for authentication when you obtain a private image. The following is an example of using the myregistrykey for authentication.

   apiVersion: v1
   kind: Pod
   metadata:
     name: foo
     namespace: default
   spec:
     containers:
       - name: foo
         image: www.3rdregistry.com/janedoe/awesomeapp:v1
     imagePullSecrets:
       - name: myregistrykey              #Use the created secret.