Registry Overview

Edka includes a managed in-cluster registry based on Zot. It runs inside your cluster and gives you a local image endpoint for builds and deployments.

Where to manage it

1. Open your cluster.
2. In the cluster sidebar, open Registry.
3. Select the Cluster Registry tab (the External Registries tab manages external credentials).

You can manage both:

• Cluster Registry: in-cluster Zot.
• External Registries: credentials such as GHCR, Docker Hub, ECR, GAR, or custom registries.

Install the in-cluster registry

Before install, configure:

• Persistent Volume Size (for example 20Gi).
• Storage Class (optional, defaults to cluster default).

Then click Install Registry.

When installed, Zot is exposed internally at:

• zot.registry.svc.cluster.local

Runtime status and usage visibility

The In-Cluster Zot Registry card on the Cluster Registry tab shows live operational state, including:

• Endpoint and namespace.
• Pods ready count.
• Workload type/name and replicas ready.
• Pod phases and total container restarts.
• Repository count and tags.
• Persistent volume usage and available capacity.
• Resource requests/limits and runtime CPU/memory usage (when Kubernetes metrics are available).
• Warnings when metrics/catalog/volume data are temporarily unavailable.

Browse repositories and delete tags

The Cluster Registry tab lists the repositories stored in Zot, with filtering and pagination. Open a repository to:

• Copy the repository reference or a ready-to-use docker pull command.
• Browse its tags, with filtering and pagination.
• Select tags and delete them, or delete every tag in the repository.

Tag deletion is permanent. Deleting a large repository can take a moment to complete.

Expand storage for an existing registry

You can expand storage after install:

1. Enter a larger PVC size than the current requested size.
2. Click Expand Storage.
3. Watch the Volume Expansion In Progress status card.

During expansion, Edka shows:

• Progress state updates.
• Target size.
• Current provisioned capacity.

Notes:

• Shrinking is not supported.
• Storage class changes are not supported after install.
• Expansion completion depends on storage backend behavior and can take several minutes.

Uninstall safety guard

Edka blocks uninstall when workloads still depend on the in-cluster Zot registry endpoint.

This prevents breaking deployments or cronjobs that still pull/push images via:

• zot.registry.svc.cluster.local

If uninstall is blocked, move dependent workloads to another registry first, then retry.

External registries on a cluster

The External Registries tab connects account-level credentials (added under Integrations > External Container Registry) to this cluster.

• Default registry: the registry Edka uses for build pushes and new deployments. Choose the in-cluster Zot registry (when installed), an applied external registry, or no default.
• Apply registry: distributes pull credentials for a registered registry to the cluster, optionally setting it as the default in the same step.
• Applied registries: each entry shows its continuous sync status (synced namespace count and last sync time) and, for AWS ECR, when the token renews next. Use Sync Now to push credentials to the cluster immediately, or Remove to stop distributing them.

The page warns when the configuration needs attention — for example when the configured default registry is not applied to the cluster, or when registries are applied but no default is set.

Credential setup and sync behavior are covered in Container Registry Integrations.

Image usage examples

# Push
docker push zot.registry.svc.cluster.local/my-app:latest

# Pull
docker pull zot.registry.svc.cluster.local/my-app:latest

Related docs

• Container Registry Integrations
• Kubernetes Clusters Overview
• Add-ons Overview