Use a Private Repository for Docker Images

This article teaches you how to use a private repository to manage your Docker images. When you install or upgrade Fusion, you can specify the private repository instead of the public repository. To find all Docker images required for your private repository, see List All Docker Images and Versions. If you’re deploying on-premises, you’ll need to set up on-premises private Docker registries.

Download the values.sh script.

Run the script: ./values.sh.

If you receive an error stating bash: ./values.sh: Permission denied:

Make the script executable: chmod +x values.sh.
Run the script again: ./values.sh.

The script creates a new file, <provider>_<cluster>_<namespace>_fusion_repository.yaml. The contents of the file resembles the following:

---

admin-ui:
  initContainer:
    image:
      repository: docker-vendorimages-local.devopsrepo.kp.org/sda
  image:
    repository: docker-vendorimages-local.devopsrepo.kp.org/sda
api-gateway:
  keytoolUtils:
    image:
      repository: "docker-vendorimages-local.devopsrepo.kp.org/sda"
  initContainer:
    image:
      repository: docker-vendorimages-local.devopsrepo.kp.org/sda
  image:
    repository: docker-vendorimages-local.devopsrepo.kp.org/sda
argo:
  images:
    ...

Open the <provider>_<cluster>_<namespace>_upgrade_fusion.sh script for editing.

Update the MY_VALUES values to refer to the <provider>_<cluster>_<namespace>_fusion_repository.yaml file:

MY_VALUES=""
MY_VALUES="$MY_VALUES --values <provider>_<cluster>_<namespace>_fusion__repository.yaml"
MY_VALUES="$MY_VALUES --values <provider>_<cluster>_<namespace>_fusion_values.yaml"
MY_VALUES="$MY_VALUES --values <provider>_<cluster>_<namespace>_fusion_resources.yaml"
MY_VALUES="$MY_VALUES --values <provider>_<cluster>_<namespace>_fusion_affinity.yaml"
MY_VALUES="$MY_VALUES --values <provider>_<cluster>_<namespace>_fusion_replicas.yaml"

Run the <provider>_<cluster>_<namespace>_upgrade_fusion.sh script.