Customer Advisory - D2iQ-2022-0003 - Air Gapped Bundle Changes

Problem Description

As we have updated all attributions, the file contents of the following downloads has changed in the support portal:

• Air-gapped Container Image Bundles, Kommander Image, v2.2.0
• Air-gapped Helm Chart Bundles, Helm Charts for Kommander and Kommander applications, v2.2.0
• Linux (Air-gapped Image Bundle), v2.1.1
• Linux (Air-gapped Image Bundle), v2.1.2
• Kaptain Air-gapped (DKP 2.x base bundle) v1.3.0
• Kaptain Air-gapped (DKP 2.x CPU bundle) v1.3.0
• Kaptain Air-gapped (DKP 2.x GPU bundle) v1.3.0
• Kaptain Air-gapped (DKP 2.x base bundle) v2.0.0
• Kaptain Air-gapped (DKP 2.x CPU bundle) v2.0.0
• Kaptain Air-gapped (DKP 2.x GPU bundle) v2.0.0

We have bundled an additional text file which requires a change to the extraction process.

Context & Symptoms

If you are using air-gapped functionality in any of the above product versions and have automation set up, update your automation to account for the additional extraction process and new file extension. You may also need to update any download links that are bookmarked or otherwise internally stored to account for the new file extension.

Note: This does not impact already installed products, only the process for future installations.

Workaround / Solution

DKP 2.2

1.  The following process must be repeated for each of the impacted files:

• downloads.d2iq.com/dkp/v2.2.0/kommander-image-bundle-v2.2.0.tar.gz
• downloads.mesosphere.io/dkp/v2.2.0/dkp-catalog-applications-image-bundle-v2.2.0.tar.gz
• downloads.mesosphere.io/dkp/v2.2.0/dkp-kommander-charts-bundle-v2.2.0.tar.gz
• downloads.mesosphere.io/dkp/v2.2.0/dkp-catalog-applications-charts-bundle-v2.2.0.tar.gz

2.  Download and untar each impacted file:

wget "https://downloads.d2iq.com/dkp/v2.2.0/kommander-image-bundle-v2.2.0.tar.gz" -O - | tar -xvf -

3.  The resulting files will be:

kommander-image-bundle-v2.2.0.tar.gz
NOTICES.txt

4.  Now use kommander-image-bundle-v2.2.0.tar.gz to run dkp push commands in the same way as before this change, when you downloaded the single tar directly.

Kommander 2.1

1.  Download and untar the impacted file:

Kommander 2.1.1

wget "https://downloads.d2iq.com/kommander/airgapped/v2.1.1/kommander_image_bundle_v2.1.1_linux_amd64.tar" -O - | tar -xvf -

Kommander 2.1.0

wget "https://downloads.d2iq.com/kommander/airgapped/v2.1.0/kommander_image_bundle_v2.1.0_linux_amd64.tar" -O - | tar -xvf -

2.  The resulting files will be:

Kommander 2.1.1

kommander_image_bundle_v2.1.1_linux_amd64.tar
NOTICES.txt

Kommander 2.1.0

kommander_image_bundle_v2.1.0_linux_amd64.tar
NOTICES.txt

3.  You can now use the tars in your scripts to push to your registry as you did before this change.

Kaptain 1.3

1.  Download the image bundle file:

1a.  Download the kaptain_air_gapped.tar file. It contains the required artifacts to perform an air-gapped installation. Extract the image bundle archive and other files before use:

tar -xvf kaptain-air-gapped.tar.gz

1b.  (Optional) Download the custom image artifacts kaptain_air_gapped_cpu.tar or kaptain_air_gapped_gpu.tar based on whether you need CPU or GPU for your workloads. To do so, extract the image bundle archive and other files before use:

tar -xvf kaptain-air-gapped.tar.gz

2.  Place the bundle in a location where you can load and push the images to your private Docker registry. Extract the image bundle archive and other files before use:

tar -xvf kaptain-air-gapped.tar.gz

3.  You can now use the .tar files in your scripts to push to your registry as you did before this change.

Kaptain 2.0

1.  Download the image bundle file:

1a.  Download the kaptain-air-gapped-2.0.0.tar.gz file. It contains the required artifacts to perform an air-gapped installation. Extract the image bundle archive and other files before use.

tar -xvf kaptain-air-gapped-2.0.0.tar.gz

1b.  (Optional) Download the custom image artifacts kaptain-air-gapped-2.0.0_cpu.tar.gz or kaptain-air-gapped-2.0.0_gpu.tar.gz based on whether you need CPU or GPU for your workloads. Extract the image bundle archive and other files before use.

tar -xvf kaptain-air-gapped-cpu.tar.gz

2.  Place the bundle in a location where you can load and push the images to your private Docker registry. Extract the image bundle archive and other files before use:

tar -xvf kaptain-air-gapped-gpu.tar.gz

3.  You can now use the tars in your scripts to push to your registry as you did before this change.

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please submit a ticket at support.d2iq.com.