docs: add note about including core content for scaleup (#5289) (#5303)

* docs: add note about including core content for scaleup * docs: minor edit * docs: clarify note * docs: minor edit (cherry picked from commit d2a269a) Co-authored-by: Lenny Chen <[email protected]>
spectrocloud · Jan 7, 2025 · b95de7e · b95de7e
1 parent 3edd7a0
commit b95de7e
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 0 deletions.
diff --git a/...content/clusters/edge/edgeforge-workflow/palette-canvos/build-content-bundle.md b/...content/clusters/edge/edgeforge-workflow/palette-canvos/build-content-bundle.md
@@ -293,6 +293,15 @@ Creating a content bundle provides several benefits that may address common use
     | `--project-id`               | The ID of your Palette project.                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
     | `--private-key`              | The path to the private key used to sign the content bundle and cluster definition if it is present. This is necessary if your Edge host has an embedded corresponding public key. For more information, refer to [Embed Public Key in Edge Artifacts](./signed-content.md).                                                                                                                                                                                                                |
 
+    :::warning
+
+    If you plan to create an airgap cluster or scale up an airgap cluster, you must ensure that you build the content
+    bundle with either the `--include-palette-content` or the `--include-core-images-only` flag. Content bundles
+    uploaded to the cluster that do not have either of these flags cannot be used to provision new nodes and will lead
+    to failure during cluster creation and scale-up.
+
+    :::
+
     The result is a content bundle that you can use to preload into your installer. The content bundle will be a zst
     file in a folder that starts with **content-** followed by a random string. For more information about how to use a
     content bundles, [Build Installer ISO](./build-installer-iso.md) or

diff --git a/docs/docs-content/clusters/edge/local-ui/cluster-management/scale-cluster.md b/docs/docs-content/clusters/edge/local-ui/cluster-management/scale-cluster.md
@@ -30,6 +30,10 @@ installed in airgap mode in Local UI.
 - You have access to the leader node of the cluster. For more information about leader host, refer to
   [Link Hosts](./link-hosts.md).
 
+- The content bundle that was last uploaded to the cluster control plane nodes was built with either the
+  `--include-palette-content` or the `--include-core-images-only` flag. For more information about building content
+  bundles, refer to [Build Content Bundle](../../edgeforge-workflow/palette-canvos/build-content-bundle.md).
+
 ### Procedure
 
 1. Log in to [Local UI](../host-management/access-console.md) on the leader node where your cluster is deployed.