Nexus Usage

If your organization has defined a docker-proxy repository on Nexus, configure registry mirrors on Kubernetes worker nodes and update image paths in Apinizer deployment files according to the Nexus address.

Info

Replace the <NEXUS_HOST> placeholder in this page with your organization's registry address. Path segments (docker-proxy, etc.) may vary based on your Nexus configuration.

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."<NEXUS_HOST>"]
  endpoint = ["https://<NEXUS_HOST>"]

Example:

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

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

{
  "data-root": "/docker-data",
  "insecure-registries": ["<NEXUS_HOST>"],
  "registry-mirrors": ["https://<NEXUS_HOST>"],
  "exec-opts": ["native.cgroupdriver=systemd"],
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "100m"
  },
  "storage-driver": "overlay2"
}

Example (registry fields):

{
  "insecure-registries": ["repo.apinizer.com"],
  "registry-mirrors": ["https://repo.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 Nexus path structure:

image: <NEXUS_HOST>/docker-proxy/apinizercloud/apimanager:<APINIZER_VERSION>

Example:

image: repo.apinizer.com/docker-proxy/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
• Harbor Usage — corporate Harbor scenario
• Apinizer Version Upgrade — Local Registry — pushing images to registry and kubectl set image