Skip to content

Commit 98c0614

Browse files
committed
clarify that builder isn't needed in all cases
1 parent 85a1dfb commit 98c0614

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

docs/vendor/helm-install-airgap.mdx

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,13 @@ Before you install, complete the following prerequisites:
1414

1515
* Declare the SDK as a dependency in your Helm chart. For more information, see [Install the SDK as a Subchart](replicated-sdk-installing#install-the-sdk-as-a-subchart) in _Installing the Replicated SDK_.
1616

17-
* Configure the HelmChart custom resource `builder` key. This ensures that the Vendor Portal can template the chart to discover the full list of container images required to install the chart in an air-gapped environment. The Vendor Portal uses this list of required images to create the Helm air gap installation instructions for the customer. For more information, see [builder](/reference/custom-resource-helmchart-v2#builder) in _HelmChart v2_.
17+
* If your Helm chart's default values do not expose all the required and optional images that might be needed to install in air-gapped environments, add the Replicated HelmChart custom resource to your release and configure `builder` key. For more information, see [builder](/reference/custom-resource-helmchart-v2#builder) in _HelmChart v2_. If your default values expose all images needed for air gap installations, you do not need to configure the `builder` key.
18+
19+
<details>
20+
<summary>What is the purpose of the `builder` key?</summary>
21+
22+
Configuring the `builder` key ensures that the Vendor Portal can template the chart to discover the full list of container images required to install the chart in an air-gapped environment. The Vendor Portal uses this list of required images to create the Helm air gap installation instructions for the customer.
23+
</details>
1824

1925
* The customer used to install must have the following:
2026

0 commit comments

Comments
 (0)