Air gap delivery considerations

When deploying a delivery in an air-gapped environment, several steps must be completed to ensure all required components are available inside the protected network. Since the latest Middle Tier version is always bundled into a new delivery from Build Place, all related container images and Helm charts must be downloaded before moving the delivery to the secure network.

Use a server with internet access Ensure work is performed on a Linux server that is not air-gapped. Refer to the image here.

Download the delivery from Build Place Retrieve the latest delivery package using your standard procedure.

Identify the Middle Tier version Open the downloaded delivery and locate the version.yaml file inside the ifsinstaller folder. This file contains the serviceUpdate value, which indicates the Middle Tier version to be downloaded.

Download images and Helm charts Use the download.sh script to fetch the container images and Helm charts corresponding to the serviceUpdate version. This version should be used as the release identifier during the download process. Read how to download a release here

Transfer to the protected network Move both the delivery and the downloaded images/charts to the internal repository within the air-gapped environment. Then proceed with the standard delivery deployment steps.

Note: If a local security patch delivery was created on your server with internet access, the process above also needs to be followed.