Pulling images from Replicated registry

When installing an application on a server that has internet access, private images can be served from Replicated registry. Authentication will be performed with license_id. This can be used with the docker login command or as Kubernetes registry secrets. In the following example, a Kubernetes secret is created in order to pull a private image from Replicated registry.

Shipping a Docker Registry for airgap installations

When distributing a Kubernetes (or Helm) application, most customers will be able to provide a Docker registry that required application images can be pushed to. Replicated Ship can retag and rewrite the Kubernetes YAML to work in this scenario.

If the Kubernetes cluster ] was set up using the Replicated Kubernetes installer, a Docker registry might not be available. The Replicated Kubernetes installer will pre-pull the registry:2 image on all nodes in the cluster.

Docker Registry Assets

To start, include the following assets in a Ship release. These define the Docker registry, and will help get the registry bootstrapped into the cluster. Note that the imagePullPolicy in the pod is set to Never because the cluster should not attempt to pull the image from Docker Hub, and instead expect that the image will already be present.