Akasha.
DocsAbout managed KubernetesContainer registry

Container registry

Run a Zot OCI registry on a cluster, browse images in the console, configure authentication, and push and pull images.

Each cluster can run its own OCI container registry, powered by Zot. Install it with the Zot Registry add-on (it is included in the CI & CD bundle and requires a storage add-on). The registry stores images inside the cluster, close to your workloads.

Browse images

  1. Go to Kubernetes → Registry. Clusters with the registry add-on are listed; if none appear, install the Zot Registry add-on from a cluster's Resource tab first.
  2. Select a cluster and open the Images tab.
  3. Click a repository to list its tags. Each tag row includes a copyable docker pull command.

Push and pull images

Pushes and pulls go directly to the cluster's registry endpoint — not through the console. The Configuration tab's Registry Access section shows the endpoint for your cluster together with ready-made docker login, docker tag, docker push, and docker pull commands:

docker login <registry-endpoint>
docker tag myapp:latest <registry-endpoint>/myapp:latest
docker push <registry-endpoint>/myapp:latest

The exact endpoint address, port, and TLS setup are specific to your deployment — copy the commands from the Registry Access section, and ask your administrator if the endpoint is not reachable from where you build images.

Configure authentication

By default the registry accepts unauthenticated access. To require credentials, the registry uses htpasswd-style users (bcrypt). The Configuration tab includes a Quick Auth Setup guide:

  1. Generate a password hash on your machine:

    htpasswd -nbBC 10 admin yourpassword

    If you do not have htpasswd installed, the console also shows an equivalent docker run command.

  2. Click Load Auth Template to inject an authentication template into the Helm values editor, and paste your user:hash entry into the htpasswd section.

  3. Save the values. The registry restarts with authentication enabled.

After enabling auth, docker login with the configured user before pushing or pulling.

Advanced configuration

The Configuration tab's Helm Values editor exposes the registry's full live Helm values. Saving applies the change as a queued operation, the same way add-on values are updated.

Use it for Helm charts and OCI artifacts

Zot is a general OCI registry: besides container images, it can store Helm charts (helm push chart.tgz oci://<registry-endpoint>/charts) and serve as an OCI source for GitOps with Flux.