Harbor Usage

If your organization uses Harbor registry, configure registry mirrors on Kubernetes worker nodes and update image paths in Apinizer deployment files according to the Harbor address. Obtain the registry host and project path from your organization.

Info

Replace the <HARBOR_HOST> and <HARBOR_PROJECT> placeholders in this page with your organization's Harbor address and project name.

Node Configuration

Apply this configuration on all worker nodes in the cluster. Select the tab matching the container runtime used on your nodes.

Containerd

Modern Kubernetes installations use containerd. Switch to the root user and open the configuration file:

sudo su
vi /etc/containerd/config.toml

Add the mirror definition under [plugins."io.containerd.grpc.v1.cri".registry]:

[plugins."io.containerd.grpc.v1.cri".registry.mirrors."<HARBOR_HOST>"]
  endpoint = ["https://<HARBOR_HOST>"]

Example:

[plugins."io.containerd.grpc.v1.cri".registry.mirrors."harbor.apinizer.com"]
  endpoint = ["https://harbor.apinizer.com"]

If Harbor uses a corporate CA certificate, copy the certificate to the node and add the TLS definition as well:

[plugins."io.containerd.grpc.v1.cri".registry.configs."<HARBOR_HOST>".tls]
  ca_file = "/etc/containerd/certs.d/<HARBOR_HOST>/ca.crt"

Restart the containerd service to apply the change:

systemctl restart containerd
systemctl status containerd

Docker

On nodes using the Docker runtime, edit /etc/docker/daemon.json:

sudo su
vi /etc/docker/daemon.json

If Harbor uses HTTPS and requires a corporate CA certificate, add the certificate to the system. For HTTP or self-signed environments, insecure-registries can be used:

{
  "insecure-registries": ["<HARBOR_HOST>"]
}

Example:

{
  "insecure-registries": ["harbor.apinizer.com"]
}

Restart the Docker service to apply the change:

systemctl daemon-reload
systemctl restart docker
docker info

Kubernetes Deployment Configuration

Update the image field in Deployment, StatefulSet, or Helm values files according to your Harbor path structure:

image: <HARBOR_HOST>/<HARBOR_PROJECT>/apinizercloud/apimanager:<APINIZER_VERSION>

Example:

image: harbor.apinizer.com/apinizer/apinizercloud/apimanager:2026.01.1

The same path pattern is used for the other components (worker, cache, integration, apiportal).

Related Documentation

• Container Images and Registry — scenario selection and common image list
• Nexus Usage — corporate Nexus scenario
• Apinizer Version Upgrade — Local Registry — pushing images to registry and kubectl set image