Container Images and Registry
Apinizer components are distributed as container images in Kubernetes environments. In environments without direct internet access or those using corporate registries (Nexus, Harbor, etc.), registry configuration must be applied on cluster nodes and the image fields in deployment files must be updated accordingly.
Which Scenario Applies to You?
Pulling images via corporate Nexus docker-proxy with containerd and deployment configuration
Image access and deployment configuration via corporate Harbor registry
Setting up your own Docker Distribution registry, uploading images, and using them in Kubernetes
Transferring images as .tar files or pushing to a local registry (version upgrade)
Apinizer Container Images
Apinizer images are published on Docker Hub under two organizations. The version you install determines the organization:
| Organization | Version type | Example version | Purpose |
|---|---|---|---|
apinizercloud | Major release (YYYY.MM.0) | 2026.10.0 | The main release that contains new features. Published every 4 months. |
apinizerpatch | Patch release (YYYY.MM.N, N ≥ 1) | 2027.01.1 | Contains bug fixes and security updates for a major release. It does not add new dependencies or breaking changes. |
This split starts with the 2027.01 major release: patch releases 2027.01.1 and later are in the apinizerpatch organization. All 2026 releases (patch releases included, e.g. 2026.10.4) are in the apinizercloud organization.
The image names are the same in both organizations:
| Component | Image name |
|---|---|
| API Manager | <ORGANIZATION>/apimanager |
| Worker | <ORGANIZATION>/worker |
| Cache | <ORGANIZATION>/cache |
| Integration | <ORGANIZATION>/integration |
| API Portal | <ORGANIZATION>/apiportal |
Replace <ORGANIZATION> with apinizercloud or apinizerpatch according to the version type, and <APINIZER_VERSION> with the version you are installing or upgrading to. Example: apinizercloud/worker:2026.10.0, apinizerpatch/worker:2027.01.1.
Image Field in Deployment Files
When using a corporate registry, update the image field according to your organization's registry host and path structure:
image: <REGISTRY_HOST>/<REGISTRY_PATH>/<ORGANIZATION>/apimanager:<APINIZER_VERSION>
Example:
image: repo.apinizer.com/docker-proxy/apinizercloud/apimanager:2026.10.0
The image names listed in the table above are used with the same pattern for the other components.
Registry configuration must be consistent across all Kubernetes worker nodes. After changing configuration, test image pull on each node.
Related Documentation
- Kubernetes Setup — default image pull and deployment steps
- Apinizer Version Upgrade — Local Registry — image push and
kubectl set imagesteps in offline environments - Kubernetes, Docker and Containerd Troubleshooting —
ImagePullBackOff, certificate errors, etc.