Control Plane can pull container images from public or private Docker compatible repositories. Pull secrets are required when pulling images from private repositories or from another Control Plane Org. When using the Control Plane built-in private image repository provided for your org, a pull secret is not required.
The user following the steps below must be a member of the superusers group or have the following permissions within a policy:
Optional:
Use the following formats when pulling from a public repository:
public.ecr.aws/REGISTRY-ALIAS/IMAGE_NAME:TAG
IMAGE_NAME:TAG
gcr.io/REGISTRY/IMAGE_NAME:TAG
ghcr.io/OWNER/IMAGE_NAME:TAG
Secrets
in the left menu and click New
, orCreate
dropdown in the upper right corner and select Secret
.Secret Type
dropdown, select one of the following:Next (Tags)
.Create
. The secret has been successfully created.If you wish, the CLI can be used instead of the console.
GVC
in the left menu and click the Pull Secrets
link.Add
button, select the secret created in step 1 and click OK
.Save
. The secret is now associated with the GVC as a Pull Secret.Refer to the Create a Workload guide and Workload reference page to create/manage your workload.
For the step where the image name is entered, follow the syntax below for the target registry:
Registry:
/org/ORG_NAME/image/IMAGE_NAME:TAG
or //image/IMAGE_NAME:TAG
ORG_NAME.registry.cpln.io/IMAGE_NAME:TAG
AWS_ACCOUNT_ID.dkr.ecr.REGION.amazonaws.com/IMAGE_NAME:TAG
REGISTRY.azurecr.io
IMAGE_NAME:TAG
gcr.io/IMAGE_NAME:TAG
ghcr.io/OWNER/IMAGE_NAME:TAG
After creating or saving the Workload, a new deployment will be queued. Click on the Deployments
link to view the deployment
status. If there is an error (i.e. authentication failed), it will be display under each deployment.