Connect Image Registry

Check the config template is exist with the following command:

There are two ways to create the config. On the Configs page, you could create the configs that belong to the system scope. Then, the Image registry could be used for all projects. If you only want to use it for one project, let’s create the config on the Project summary page.

On the page, let’s create a private image registry with the following fields:

Your image registry domain, such as index.docker.io. Please make sure this domain could be accessed from all cluster nodes.

If your registry server uses the self-signed certificate, you should enable this field. This only means KubeVela could trust your registry. You also need to make sure the or containerd in your cluster node trust this registry. refer to: .

If your registry needs authentication, you need must set the username and password. KubeVela will generate the secret and distribute it to all clusters.

Also, we could create the image registry config via CLI:

List all Image registries:

After creating a config, it only saves as a Secret in the system namespace in the hub cluster. But the application will generate the Workload resource that depends on this Secret which type is . So, we should distribute the Secret to all namespaces that we could use and include managed clusters. The config distribution could help you.

Click the Distribute button and select the targets that you want to distribute the config.

Also, you could distribute the config via CLI:

Let’s follow the Deploy Container Image to create an application. After you input the image name, KubeVela will automatically identify the matched registries.