Registry setup
Configure image registry credentials for online and air-gapped SMP Operator installations.
Online install
For online installations, the operator pulls images from the Harness public registry.
The following table lists each registry the installation reaches and the images it provides.
pkg.harness.io/g_ix-gj_sisgiituoe06eq/cxe-public-docker
platform-installer-min, tiw-airgap
registry.k8s.io
ingress-nginx/controller, ingress-nginx/kube-webhook-certgen
registry.istio.io/release
pilot, proxyv2 (only if using Istio)
Air-gapped and private registry
For air-gapped environments, mirror all images to your private registry before you install.
Required images
Mirror each of the following images. The Version Matches column tells you which version to use for each one.
platform-installer-min
pkg.harness.io/.../cxe-public-docker
clustermgr version (e.g., 1.0.6)
tiw-airgap
pkg.harness.io/.../cxe-public-docker
workflow version (e.g., 0.43.0)
ingress-nginx/controller
registry.k8s.io
v1.15.1
ingress-nginx/kube-webhook-certgen
registry.k8s.io
v1.6.9
release/pilot
registry.istio.io
1.30.3 (only if using Istio)
release/proxyv2
registry.istio.io
1.30.3 (only if using Istio)
Mirror images
Run the following commands to pull each image, retag it for your private registry, and push it. Replace the variable values with your own registry details.
Istio images
Run these additional commands only if you use Istio.
Registry flags
Provide your registry details to the installation so the operator can authenticate and pull images.
When you install with Helm, set the registry details in values.yaml under cluster.
cluster.imageRegistryHost
Registry hostname
pkg.harness.io/g_ix-gj_sisgiituoe06eq
cluster.imageRegistryPathPrefix
Path prefix within the registry
cxe-public-docker
cluster.imageRegistryUsername
Registry username
admin
cluster.imageRegistryPassword
Registry password or token
pat.xxx.xxx
When you install with clustermgr, pass the registry details as flags.
--registry-host
Registry hostname
registry.example.com
--registry-prefix
Path prefix within the registry
harness-platform
--registry-user
Registry username
admin
--registry-password
Registry password or token
pat.xxx.xxx
Last updated
Was this helpful?