Repository: spectrocloud/librarium
Pull request #6683: docs: add requirements of pack.content.images
Author: login: lennessyy
Labels: name: auto-backport
description: Enable backport
name: released
name: backport-version-4-6
description: Backport change to version 4.6
Created: 2025-05-06T20:31:47Z | Merged: 2025-05-07T18:38:43Z

## Describe the Change

<!-- Add a description of what the pull request is changing, adding, and any other relevant context.  -->

This PR adds the requirements that images must be specified in the `pack.content.images` list. 

## Changed Pages

<!-- Add a link to the preview URL generated by Netlify. Include direct links to the pages affected by the PR. -->

💻 [Add Preview URL for Page]()

## Jira Tickets

<!-- Add a link to the JIRA tickets (if applicable) -->

🎫 [PE-6557](https://spectrocloud.atlassian.net/browse/PE-6557)

## Backports

<!-- Add the relevant backport labels to reflect which versions of the docs your changes will affect. -->

Can this PR be backported?

- [x] Yes. _Remember to add the relevant backport labels to your PR._
- [ ] No. _Please leave a short comment below about why this PR cannot be backported._


[PE-6557]: https://spectrocloud.atlassian.net/browse/PE-6557?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ


Diff:
diff --git a/docs/docs-content/registries-and-packs/add-custom-packs.md b/docs/docs-content/registries-and-packs/add-custom-packs.md
index e32fab7da42..8e30b29a010 100644
--- a/docs/docs-content/registries-and-packs/add-custom-packs.md
+++ b/docs/docs-content/registries-and-packs/add-custom-packs.md
@@ -257,47 +257,63 @@ Follow the steps below to create a custom pack.
 3. Create a file named `values.yaml`. This file consists of configurable parameters that need to be exposed to the
    end-users during the creation of a cluster profile.
 
-:::info
-
-A values.yaml file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but an
-empty file still needs to be added to the OS pack.
-
-:::
+   :::info
+
+   A `values.yaml` file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but
+   an empty file still needs to be added to the OS pack.
+
+   :::
+
+   Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
+   natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need
+   to be explicitly configured to use parameters if desired.
+
+   ```yaml
+   pack:
+      namespace : <default namespace for charts and manifests>
+   charts:
+      chart1:
+      <configurable chart1 parameters>
+      chart2:
+      <configurable chart2 parameters>
+   manifests:
+      manifest1:
+          <manifest1 parameters>
+      manifest2:
+          <manifest2 parameters>
+   ```
 
-Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
-natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need to
-be explicitly configured to use parameters if desired.
+4. (Optional) If you are designing a pack that can be used in Edge cluster profiles in the `local` management mode,
+   ensure you include all images that are referenced in the pack in the `pack.content.images` section of the
+   `values.yaml` file. For more information about local deployments with primary registries, refer to
+   [Deploy with a Primary Registry](../clusters/edge/site-deployment/deploy-custom-registries/deploy-primary-registry.md).
+
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
 
-```yaml
-    pack:
-        namespace : <default namespace for charts and manifests>
-    charts:
-        chart1:
-        <configurable chart1 parameters>
-        chart2:
-        <configurable chart2 parameters>
-    manifests:
-        manifest1:
-            <manifest1 parameters>
-        manifest2:
-            <manifest2 parameters>
-```
+   If you do not specify the images in the `pack.content.images` field and your cluster is a local cluster with an
+   in-cluster primary registry, the images will not be loaded and deployment of the application will fail.
 
-4. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
+5. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
 
-5. Login to the pack registry using the following command:
+6. Log in to the pack registry using the following command.
 
    ```bash
     spectro registry login [REGISTRY_SERVER]
    ```
 
-6. Push the newly defined pack to the pack registry using the following command:
+7. Push the newly defined pack to the pack registry using the following command.
 
    ```bash
     spectro pack push [PACK_DIR_LOCATION] --registry-server [REGISTRY_SERVER]
    ```
 
-7. To overwrite contents of a previously deployed pack, use the force option as follows:
+8. To overwrite contents of a previously deployed pack, use the force option as follows.
 
    ```bash
     spectro pack push [PACK_DIR_LOCATION] -f --registry-server [REGISTRY_SERVER]
diff --git a/docs/docs-content/registries-and-packs/adding-add-on-packs.md b/docs/docs-content/registries-and-packs/adding-add-on-packs.md
index 130a98f923d..59af3001d93 100644
--- a/docs/docs-content/registries-and-packs/adding-add-on-packs.md
+++ b/docs/docs-content/registries-and-packs/adding-add-on-packs.md
@@ -27,8 +27,6 @@ examples to create custom add-on packs.
 
 - [Manifests](#manifests)
 
-<br />
-
 ## Helm Charts
 
 The following example shows how to build the Prometheus-Grafana monitoring pack and push to a pack registry server using
@@ -224,13 +222,28 @@ the Spectro Cloud CLI:
     ...
    ```
 
-6. Log in to the pack registry using the following command:
+6. (Optional) If you are designing a pack that can be used in Edge cluster profiles in the `local` management mode,
+   ensure you include all images that are referenced in the pack in the `pack.content.images` section of the
+   `values.yaml` file.
+
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
+
+   If you do not specify the images in the `pack.content.images` field and your cluster is a local cluster with an
+   in-cluster primary registry, the images will not be loaded and deployment of the application will fail.
+
+7. Log in to the pack registry using the following command:
 
    ```bash
     spectro registry login [REGISTRY_SERVER]
    ```
 
-7. Using the Spectro CLI, push the newly built pack to the pack registry:
+8. Using the Spectro CLI, push the newly built pack to the pack registry.
 
    ```bash
     spectro pack push prometheus-grafana --registry-server [REGISTRY-SERVER]
@@ -387,8 +400,6 @@ Spectro Cloud CLI.
 
 5. Create a file called `values.yaml` to provide configurable manifest parameters.
 
-   **values.yaml:**
-
    ```yaml
    manifests:
      permission-manager:
@@ -399,13 +410,29 @@ Spectro Cloud CLI.
        authPassword: "welcome123"
    ```
 
-6. Log in to the pack registry using the following command:
+6. (Optional) If you are designing a pack that can be used in Edge cluster profiles in the `local` management mode,
+   ensure you include all images that are referenced in the pack in the `pack.content.images` section of the
+   `values.yaml` file. For more information about local deployments with primary registries, refer to
+   [Deploy with a Primary Registry](../clusters/edge/site-deployment/deploy-custom-registries/deploy-primary-registry.md).
+
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
+
+   If you do not specify the images in the `pack.content.images` field and your cluster is a local cluster with an
+   in-cluster primary registry, the images will not be loaded and deployment of the application will fail.
+
+7. Log in to the pack registry using the following command.
 
    ```bash
     spectro registry login [REGISTRY_SERVER]
    ```
 
-7. Using Spectro Cloud CLI push the newly built pack to the pack registry:
+8. Using Spectro Cloud CLI push the newly built pack to the pack registry.
 
    ```bash
     spectro pack push permission-manager --registry-server [REGISTRY-SERVER]


Reviews:
user: login: github-actions[bot]
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-06T20:35:07Z
user: login: github-actions[bot]
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-07T00:24:52Z
user: login: benradstone
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-07T08:25:38Z
user: login: benradstone
body: Approved, I would merge the open Vale suggestion though.
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-05-07T08:28:26Z
user: login: lennessyy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-07T18:27:17Z

Review comments:
diff_hunk: @@ -224,13 +224,28 @@ the Spectro Cloud CLI:
     ...
    ```
 
-6. Log in to the pack registry using the following command:
+6. (Optional) If you are designing a pack that can be used in Edge cluster profiles in local environments, ensure you
+   include all images that are referenced in the pack in the `pack.content.images` section of the `values.yaml` file.
+
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
+
+   If you do not specify the images in the `pack.content.images` field, if your Edge cluster operates in a local
+   environment without a connection to a Palette instance, the images will not be loaded and deployment of the
+   application will fail.
+
+7. Log in to the pack registry using the following command:
path: docs/docs-content/registries-and-packs/adding-add-on-packs.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.colon] Use colons only to introduce lists, unless in code blocks or inline code.
created_at: 2025-05-06T20:35:06Z
author_association: CONTRIBUTOR
diff_hunk: @@ -224,13 +224,28 @@ the Spectro Cloud CLI:
     ...
    ```
 
-6. Log in to the pack registry using the following command:
+6. (Optional) If you are designing a pack that can be used in Edge cluster profiles in local environments, ensure you
+   include all images that are referenced in the pack in the `pack.content.images` section of the `values.yaml` file.
+
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
+
+   If you do not specify the images in the `pack.content.images` field, if your Edge cluster operates in a local
+   environment without a connection to a Palette instance, the images will not be loaded and deployment of the
+   application will fail.
+
+7. Log in to the pack registry using the following command:
 
    ```bash
     spectro registry login [REGISTRY_SERVER]
    ```
 
-7. Using the Spectro CLI, push the newly built pack to the pack registry:
+8. Using the Spectro CLI, push the newly built pack to the pack registry:
path: docs/docs-content/registries-and-packs/adding-add-on-packs.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.colon] Use colons only to introduce lists, unless in code blocks or inline code.
created_at: 2025-05-06T20:35:06Z
author_association: CONTRIBUTOR
diff_hunk: @@ -399,13 +412,28 @@ Spectro Cloud CLI.
        authPassword: "welcome123"
    ```
 
-6. Log in to the pack registry using the following command:
+6. (Optional) If you are designing a pack that can be used in Edge cluster profiles in local environments, ensure you
+   include all images that are referenced in the pack in the `pack.content.images` section of the `values.yaml` file.
+
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
+
+   If you do not specify the images in the `pack.content.images` field, if your Edge cluster operates in a local
+   environment without a connection to a Palette instance, the images will not be loaded and deployment of the
+   application will fail.
+
+7. Log in to the pack registry using the following command:
path: docs/docs-content/registries-and-packs/adding-add-on-packs.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.colon] Use colons only to introduce lists, unless in code blocks or inline code.
created_at: 2025-05-06T20:35:06Z
author_association: CONTRIBUTOR
diff_hunk: @@ -399,13 +412,28 @@ Spectro Cloud CLI.
        authPassword: "welcome123"
    ```
 
-6. Log in to the pack registry using the following command:
+6. (Optional) If you are designing a pack that can be used in Edge cluster profiles in local environments, ensure you
+   include all images that are referenced in the pack in the `pack.content.images` section of the `values.yaml` file.
+
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
+
+   If you do not specify the images in the `pack.content.images` field, if your Edge cluster operates in a local
+   environment without a connection to a Palette instance, the images will not be loaded and deployment of the
+   application will fail.
+
+7. Log in to the pack registry using the following command:
 
    ```bash
     spectro registry login [REGISTRY_SERVER]
    ```
 
-7. Using Spectro Cloud CLI push the newly built pack to the pack registry:
+8. Using Spectro Cloud CLI push the newly built pack to the pack registry:
path: docs/docs-content/registries-and-packs/adding-add-on-packs.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.colon] Use colons only to introduce lists, unless in code blocks or inline code.
created_at: 2025-05-06T20:35:06Z
author_association: CONTRIBUTOR
diff_hunk: @@ -257,47 +257,62 @@ Follow the steps below to create a custom pack.
 3. Create a file named `values.yaml`. This file consists of configurable parameters that need to be exposed to the
    end-users during the creation of a cluster profile.
 
-:::info
-
-A values.yaml file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but an
-empty file still needs to be added to the OS pack.
+   :::info
+
+   A values.yaml file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but
path: docs/docs-content/registries-and-packs/add-custom-packs.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.file-type] Incorrect file type reference. Use 'YAML file'.
created_at: 2025-05-06T20:35:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -257,47 +257,62 @@ Follow the steps below to create a custom pack.
 3. Create a file named `values.yaml`. This file consists of configurable parameters that need to be exposed to the
    end-users during the creation of a cluster profile.
 
-:::info
-
-A values.yaml file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but an
-empty file still needs to be added to the OS pack.
+   :::info
+
+   A values.yaml file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but
+   an empty file still needs to be added to the OS pack.
+
+   :::
path: docs/docs-content/registries-and-packs/add-custom-packs.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.colon] Use colons only to introduce lists, unless in code blocks or inline code.
created_at: 2025-05-06T20:35:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -257,47 +257,62 @@ Follow the steps below to create a custom pack.
 3. Create a file named `values.yaml`. This file consists of configurable parameters that need to be exposed to the
    end-users during the creation of a cluster profile.
 
-:::info
-
-A values.yaml file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but an
-empty file still needs to be added to the OS pack.
+   :::info
+
+   A values.yaml file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but
+   an empty file still needs to be added to the OS pack.
+
+   :::
+
+   Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
+   natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need
+   to be explicitly configured to use parameters if desired.
+
+   ```yaml
+   pack:
+      namespace : <default namespace for charts and manifests>
+   charts:
+      chart1:
+      <configurable chart1 parameters>
+      chart2:
+      <configurable chart2 parameters>
+   manifests:
+      manifest1:
+          <manifest1 parameters>
+      manifest2:
+          <manifest2 parameters>
+   ```
 
-:::
+4. (Optional) If you are designing a pack that can be used in Edge cluster profiles in local environments, ensure you
+   include all images that are referenced in the pack in the `pack.content.images` section of the `values.yaml` file.
 
-Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
-natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need to
-be explicitly configured to use parameters if desired.
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
 
-```yaml
-    pack:
-        namespace : <default namespace for charts and manifests>
-    charts:
-        chart1:
-        <configurable chart1 parameters>
-        chart2:
-        <configurable chart2 parameters>
-    manifests:
-        manifest1:
-            <manifest1 parameters>
-        manifest2:
-            <manifest2 parameters>
-```
+   If you do not specify the images in the `pack.content.images` field, if your Edge cluster operates in a local
+   environment without a connection to a Palette instance, the images will not be loaded and deployment of the
+   application will fail.
 
-4. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
+5. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
 
-5. Login to the pack registry using the following command:
+6. Login to the pack registry using the following command:
path: docs/docs-content/registries-and-packs/add-custom-packs.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.colon] Use colons only to introduce lists, unless in code blocks or inline code.
created_at: 2025-05-06T20:35:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -257,47 +257,62 @@ Follow the steps below to create a custom pack.
 3. Create a file named `values.yaml`. This file consists of configurable parameters that need to be exposed to the
    end-users during the creation of a cluster profile.
 
-:::info
-
-A values.yaml file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but an
-empty file still needs to be added to the OS pack.
+   :::info
+
+   A values.yaml file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but
+   an empty file still needs to be added to the OS pack.
+
+   :::
+
+   Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
+   natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need
+   to be explicitly configured to use parameters if desired.
+
+   ```yaml
+   pack:
+      namespace : <default namespace for charts and manifests>
+   charts:
+      chart1:
+      <configurable chart1 parameters>
+      chart2:
+      <configurable chart2 parameters>
+   manifests:
+      manifest1:
+          <manifest1 parameters>
+      manifest2:
+          <manifest2 parameters>
+   ```
 
-:::
+4. (Optional) If you are designing a pack that can be used in Edge cluster profiles in local environments, ensure you
+   include all images that are referenced in the pack in the `pack.content.images` section of the `values.yaml` file.
 
-Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
-natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need to
-be explicitly configured to use parameters if desired.
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
 
-```yaml
-    pack:
-        namespace : <default namespace for charts and manifests>
-    charts:
-        chart1:
-        <configurable chart1 parameters>
-        chart2:
-        <configurable chart2 parameters>
-    manifests:
-        manifest1:
-            <manifest1 parameters>
-        manifest2:
-            <manifest2 parameters>
-```
+   If you do not specify the images in the `pack.content.images` field, if your Edge cluster operates in a local
+   environment without a connection to a Palette instance, the images will not be loaded and deployment of the
+   application will fail.
 
-4. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
+5. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
 
-5. Login to the pack registry using the following command:
+6. Login to the pack registry using the following command:
 
    ```bash
     spectro registry login [REGISTRY_SERVER]
    ```
 
-6. Push the newly defined pack to the pack registry using the following command:
+7. Push the newly defined pack to the pack registry using the following command:
path: docs/docs-content/registries-and-packs/add-custom-packs.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.colon] Use colons only to introduce lists, unless in code blocks or inline code.
created_at: 2025-05-06T20:35:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -257,47 +257,63 @@ Follow the steps below to create a custom pack.
 3. Create a file named `values.yaml`. This file consists of configurable parameters that need to be exposed to the
    end-users during the creation of a cluster profile.
 
-:::info
-
-A values.yaml file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but an
-empty file still needs to be added to the OS pack.
-
-:::
+   :::info
+
+   A `values.yaml` file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but
+   an empty file still needs to be added to the OS pack.
+
+   :::
+
+   Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
+   natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need
+   to be explicitly configured to use parameters if desired.
+
+   ```yaml
+   pack:
+      namespace : <default namespace for charts and manifests>
+   charts:
+      chart1:
+      <configurable chart1 parameters>
+      chart2:
+      <configurable chart2 parameters>
+   manifests:
+      manifest1:
+          <manifest1 parameters>
+      manifest2:
+          <manifest2 parameters>
+   ```
 
-Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
-natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need to
-be explicitly configured to use parameters if desired.
+4. (Optional) If you are designing a pack that can be used in Edge cluster profiles in the `local` management mode,
+   ensure you include all images that are referenced in the pack in the `pack.content.images` section of the
+   `values.yaml` file. For more information about local deployments with primary registries, refer to
+   [Deploy with a Primary Registry](../clusters/edge/site-deployment/deploy-custom-registries/deploy-primary-registry.md).
+
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
 
-```yaml
-    pack:
-        namespace : <default namespace for charts and manifests>
-    charts:
-        chart1:
-        <configurable chart1 parameters>
-        chart2:
-        <configurable chart2 parameters>
-    manifests:
-        manifest1:
-            <manifest1 parameters>
-        manifest2:
-            <manifest2 parameters>
-```
+   If you do not specify the images in the `pack.content.images` field and your cluster is a local cluster with an
+   in-cluster primary registry, the images will not be loaded and deployment of the application will fail.
 
-4. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
+5. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
 
-5. Login to the pack registry using the following command:
+6. Log in to the pack registry using the following command:
path: docs/docs-content/registries-and-packs/add-custom-packs.md
user: login: github-actions[bot]
body: 🚫 **[vale]** <sub>reported by [reviewdog](https://github.com/reviewdog/reviewdog) :dog:</sub><br>[spectrocloud-docs-internal.colon] Use colons only to introduce lists, unless in code blocks or inline code.
created_at: 2025-05-07T00:24:52Z
author_association: CONTRIBUTOR
diff_hunk: @@ -257,47 +257,63 @@ Follow the steps below to create a custom pack.
 3. Create a file named `values.yaml`. This file consists of configurable parameters that need to be exposed to the
    end-users during the creation of a cluster profile.
 
-:::info
-
-A values.yaml file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but an
-empty file still needs to be added to the OS pack.
-
-:::
+   :::info
+
+   A `values.yaml` file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but
+   an empty file still needs to be added to the OS pack.
+
+   :::
+
+   Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
+   natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need
+   to be explicitly configured to use parameters if desired.
+
+   ```yaml
+   pack:
+      namespace : <default namespace for charts and manifests>
+   charts:
+      chart1:
+      <configurable chart1 parameters>
+      chart2:
+      <configurable chart2 parameters>
+   manifests:
+      manifest1:
+          <manifest1 parameters>
+      manifest2:
+          <manifest2 parameters>
+   ```
 
-Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
-natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need to
-be explicitly configured to use parameters if desired.
+4. (Optional) If you are designing a pack that can be used in Edge cluster profiles in the `local` management mode,
+   ensure you include all images that are referenced in the pack in the `pack.content.images` section of the
+   `values.yaml` file. For more information about local deployments with primary registries, refer to
+   [Deploy with a Primary Registry](../clusters/edge/site-deployment/deploy-custom-registries/deploy-primary-registry.md).
+
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
 
-```yaml
-    pack:
-        namespace : <default namespace for charts and manifests>
-    charts:
-        chart1:
-        <configurable chart1 parameters>
-        chart2:
-        <configurable chart2 parameters>
-    manifests:
-        manifest1:
-            <manifest1 parameters>
-        manifest2:
-            <manifest2 parameters>
-```
+   If you do not specify the images in the `pack.content.images` field and your cluster is a local cluster with an
+   in-cluster primary registry, the images will not be loaded and deployment of the application will fail.
 
-4. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
+5. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
 
-5. Login to the pack registry using the following command:
+6. Log in to the pack registry using the following command:
path: docs/docs-content/registries-and-packs/add-custom-packs.md
user: login: benradstone
body: Agree with Vale here.
created_at: 2025-05-07T08:25:38Z
author_association: CONTRIBUTOR
diff_hunk: @@ -257,47 +257,63 @@ Follow the steps below to create a custom pack.
 3. Create a file named `values.yaml`. This file consists of configurable parameters that need to be exposed to the
    end-users during the creation of a cluster profile.
 
-:::info
-
-A values.yaml file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but an
-empty file still needs to be added to the OS pack.
-
-:::
+   :::info
+
+   A `values.yaml` file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but
+   an empty file still needs to be added to the OS pack.
+
+   :::
+
+   Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
+   natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need
+   to be explicitly configured to use parameters if desired.
+
+   ```yaml
+   pack:
+      namespace : <default namespace for charts and manifests>
+   charts:
+      chart1:
+      <configurable chart1 parameters>
+      chart2:
+      <configurable chart2 parameters>
+   manifests:
+      manifest1:
+          <manifest1 parameters>
+      manifest2:
+          <manifest2 parameters>
+   ```
 
-Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
-natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need to
-be explicitly configured to use parameters if desired.
+4. (Optional) If you are designing a pack that can be used in Edge cluster profiles in the `local` management mode,
+   ensure you include all images that are referenced in the pack in the `pack.content.images` section of the
+   `values.yaml` file. For more information about local deployments with primary registries, refer to
+   [Deploy with a Primary Registry](../clusters/edge/site-deployment/deploy-custom-registries/deploy-primary-registry.md).
+
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
 
-```yaml
-    pack:
-        namespace : <default namespace for charts and manifests>
-    charts:
-        chart1:
-        <configurable chart1 parameters>
-        chart2:
-        <configurable chart2 parameters>
-    manifests:
-        manifest1:
-            <manifest1 parameters>
-        manifest2:
-            <manifest2 parameters>
-```
+   If you do not specify the images in the `pack.content.images` field and your cluster is a local cluster with an
+   in-cluster primary registry, the images will not be loaded and deployment of the application will fail.
 
-4. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
+5. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
 
-5. Login to the pack registry using the following command:
+6. Log in to the pack registry using the following command:
path: docs/docs-content/registries-and-packs/add-custom-packs.md
user: login: lennessyy
body: ```suggestion
6. Log in to the pack registry using the following command.
```
created_at: 2025-05-07T17:22:41Z
author_association: CONTRIBUTOR
diff_hunk: @@ -399,13 +410,29 @@ Spectro Cloud CLI.
        authPassword: "welcome123"
    ```
 
-6. Log in to the pack registry using the following command:
+6. (Optional) If you are designing a pack that can be used in Edge cluster profiles in the `local` management mode,
+   ensure you include all images that are referenced in the pack in the `pack.content.images` section of the
+   `values.yaml` file. For more information about local deployments with primary registries, refer to
+   [Deploy with a Primary Registry](../clusters/edge/site-deployment/deploy-custom-registries/deploy-primary-registry.md).
+
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
+
+   If you do not specify the images in the `pack.content.images` field and your cluster is a local cluster with an
+   in-cluster primary registry, the images will not be loaded and deployment of the application will fail.
+
+7. Log in to the pack registry using the following command:
path: docs/docs-content/registries-and-packs/adding-add-on-packs.md
user: login: lennessyy
body: ```suggestion
7. Log in to the pack registry using the following command.
```
created_at: 2025-05-07T17:22:54Z
author_association: CONTRIBUTOR
diff_hunk: @@ -224,13 +222,28 @@ the Spectro Cloud CLI:
     ...
    ```
 
-6. Log in to the pack registry using the following command:
+6. (Optional) If you are designing a pack that can be used in Edge cluster profiles in the `local` management mode,
+   ensure you include all images that are referenced in the pack in the `pack.content.images` section of the
+   `values.yaml` file.
+
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
+
+   If you do not specify the images in the `pack.content.images` field and your cluster is a local cluster with an
+   in-cluster primary registry, the images will not be loaded and deployment of the application will fail.
+
+7. Log in to the pack registry using the following command:
 
    ```bash
     spectro registry login [REGISTRY_SERVER]
    ```
 
-7. Using the Spectro CLI, push the newly built pack to the pack registry:
+8. Using the Spectro CLI, push the newly built pack to the pack registry:
path: docs/docs-content/registries-and-packs/adding-add-on-packs.md
user: login: lennessyy
body: ```suggestion
8. Using the Spectro CLI, push the newly built pack to the pack registry.
```
created_at: 2025-05-07T17:23:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -257,47 +257,63 @@ Follow the steps below to create a custom pack.
 3. Create a file named `values.yaml`. This file consists of configurable parameters that need to be exposed to the
    end-users during the creation of a cluster profile.
 
-:::info
-
-A values.yaml file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but an
-empty file still needs to be added to the OS pack.
-
-:::
+   :::info
+
+   A `values.yaml` file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but
+   an empty file still needs to be added to the OS pack.
+
+   :::
+
+   Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
+   natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need
+   to be explicitly configured to use parameters if desired.
+
+   ```yaml
+   pack:
+      namespace : <default namespace for charts and manifests>
+   charts:
+      chart1:
+      <configurable chart1 parameters>
+      chart2:
+      <configurable chart2 parameters>
+   manifests:
+      manifest1:
+          <manifest1 parameters>
+      manifest2:
+          <manifest2 parameters>
+   ```
 
-Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
-natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need to
-be explicitly configured to use parameters if desired.
+4. (Optional) If you are designing a pack that can be used in Edge cluster profiles in the `local` management mode,
+   ensure you include all images that are referenced in the pack in the `pack.content.images` section of the
+   `values.yaml` file. For more information about local deployments with primary registries, refer to
+   [Deploy with a Primary Registry](../clusters/edge/site-deployment/deploy-custom-registries/deploy-primary-registry.md).
+
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
 
-```yaml
-    pack:
-        namespace : <default namespace for charts and manifests>
-    charts:
-        chart1:
-        <configurable chart1 parameters>
-        chart2:
-        <configurable chart2 parameters>
-    manifests:
-        manifest1:
-            <manifest1 parameters>
-        manifest2:
-            <manifest2 parameters>
-```
+   If you do not specify the images in the `pack.content.images` field and your cluster is a local cluster with an
+   in-cluster primary registry, the images will not be loaded and deployment of the application will fail.
 
-4. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
+5. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
 
-5. Login to the pack registry using the following command:
+6. Log in to the pack registry using the following command:
 
    ```bash
     spectro registry login [REGISTRY_SERVER]
    ```
 
-6. Push the newly defined pack to the pack registry using the following command:
+7. Push the newly defined pack to the pack registry using the following command:
path: docs/docs-content/registries-and-packs/add-custom-packs.md
user: login: lennessyy
body: ```suggestion
7. Push the newly defined pack to the pack registry using the following command.
```
created_at: 2025-05-07T17:23:11Z
author_association: CONTRIBUTOR
diff_hunk: @@ -257,47 +257,63 @@ Follow the steps below to create a custom pack.
 3. Create a file named `values.yaml`. This file consists of configurable parameters that need to be exposed to the
    end-users during the creation of a cluster profile.
 
-:::info
-
-A values.yaml file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but an
-empty file still needs to be added to the OS pack.
-
-:::
+   :::info
+
+   A `values.yaml` file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but
+   an empty file still needs to be added to the OS pack.
+
+   :::
+
+   Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
+   natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need
+   to be explicitly configured to use parameters if desired.
+
+   ```yaml
+   pack:
+      namespace : <default namespace for charts and manifests>
+   charts:
+      chart1:
+      <configurable chart1 parameters>
+      chart2:
+      <configurable chart2 parameters>
+   manifests:
+      manifest1:
+          <manifest1 parameters>
+      manifest2:
+          <manifest2 parameters>
+   ```
 
-Parameters for all charts and manifests defined in the pack are defined in the `values.yaml` file. _Helm_ charts
-natively support values override. Any values defined are merged with those defined within a chart. _Manifests_ need to
-be explicitly configured to use parameters if desired.
+4. (Optional) If you are designing a pack that can be used in Edge cluster profiles in the `local` management mode,
+   ensure you include all images that are referenced in the pack in the `pack.content.images` section of the
+   `values.yaml` file. For more information about local deployments with primary registries, refer to
+   [Deploy with a Primary Registry](../clusters/edge/site-deployment/deploy-custom-registries/deploy-primary-registry.md).
+
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
 
-```yaml
-    pack:
-        namespace : <default namespace for charts and manifests>
-    charts:
-        chart1:
-        <configurable chart1 parameters>
-        chart2:
-        <configurable chart2 parameters>
-    manifests:
-        manifest1:
-            <manifest1 parameters>
-        manifest2:
-            <manifest2 parameters>
-```
+   If you do not specify the images in the `pack.content.images` field and your cluster is a local cluster with an
+   in-cluster primary registry, the images will not be loaded and deployment of the application will fail.
 
-4. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
+5. A pack must have the logo file named `logo.png` and must be copied into the pack directory.
 
-5. Login to the pack registry using the following command:
+6. Log in to the pack registry using the following command:
 
    ```bash
     spectro registry login [REGISTRY_SERVER]
    ```
 
-6. Push the newly defined pack to the pack registry using the following command:
+7. Push the newly defined pack to the pack registry using the following command:
 
    ```bash
     spectro pack push [PACK_DIR_LOCATION] --registry-server [REGISTRY_SERVER]
    ```
 
-7. To overwrite contents of a previously deployed pack, use the force option as follows:
+8. To overwrite contents of a previously deployed pack, use the force option as follows:
path: docs/docs-content/registries-and-packs/add-custom-packs.md
user: login: lennessyy
body: ```suggestion
8. To overwrite contents of a previously deployed pack, use the force option as follows.
```
created_at: 2025-05-07T17:23:17Z
author_association: CONTRIBUTOR
diff_hunk: @@ -399,13 +410,29 @@ Spectro Cloud CLI.
        authPassword: "welcome123"
    ```
 
-6. Log in to the pack registry using the following command:
+6. (Optional) If you are designing a pack that can be used in Edge cluster profiles in the `local` management mode,
+   ensure you include all images that are referenced in the pack in the `pack.content.images` section of the
+   `values.yaml` file. For more information about local deployments with primary registries, refer to
+   [Deploy with a Primary Registry](../clusters/edge/site-deployment/deploy-custom-registries/deploy-primary-registry.md).
+
+   ```yaml
+   pack:
+     content:
+       images:
+         - docker.io/example-image:latest
+         - gcr.io/example-image-two:latest
+   ```
+
+   If you do not specify the images in the `pack.content.images` field and your cluster is a local cluster with an
+   in-cluster primary registry, the images will not be loaded and deployment of the application will fail.
+
+7. Log in to the pack registry using the following command:
 
    ```bash
     spectro registry login [REGISTRY_SERVER]
    ```
 
-7. Using Spectro Cloud CLI push the newly built pack to the pack registry:
+8. Using Spectro Cloud CLI push the newly built pack to the pack registry:
path: docs/docs-content/registries-and-packs/adding-add-on-packs.md
user: login: lennessyy
body: ```suggestion
8. Using Spectro Cloud CLI push the newly built pack to the pack registry.
```
created_at: 2025-05-07T17:23:26Z
author_association: CONTRIBUTOR

PR comments:
user: login: netlify[bot]
created_at: 2025-05-06T20:35:23Z
body: ### <span aria-hidden="true">✅</span> Deploy Preview for *docs-spectrocloud* ready!


|  Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | e1f22dcc334999e383e93be88fdfcb2a13d0328d |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/docs-spectrocloud/deploys/681ba627000207000868ac3b |
|<span aria-hidden="true">😎</span> Deploy Preview | [https://deploy-preview-6683--docs-spectrocloud.netlify.app](https://deploy-preview-6683--docs-spectrocloud.netlify.app) |
|<span aria-hidden="true">📱</span> Preview on mobile | <details><summary> Toggle QR Code... </summary><br /><br />![QR Code](https://app.netlify.com/qr-code/eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1cmwiOiJodHRwczovL2RlcGxveS1wcmV2aWV3LTY2ODMtLWRvY3Mtc3BlY3Ryb2Nsb3VkLm5ldGxpZnkuYXBwIn0.LqpWGDrydTcuNW4cNo04A-bP7TIk-mptckvZPzzakBg)<br /><br />_Use your smartphone camera to open QR code link._</details> |
---
<!-- [docs-spectrocloud Preview](https://deploy-preview-6683--docs-spectrocloud.netlify.app) -->
_To edit notification comments on pull requests, go to your [Netlify site configuration](https://app.netlify.com/sites/docs-spectrocloud/configuration/notifications#deploy-webhooks)._
author_association: NONE
user: login: vault-token-factory-spectrocloud[bot]
created_at: 2025-05-07T18:40:45Z
body: ## 💚 All backports created successfully

| Status | Branch | Result |
|:------:|:------:|:------|
|✅|version-4-6|[<img src="https://img.shields.io/github/pulls/detail/state/spectrocloud/librarium/6725">](https://github.com/spectrocloud/librarium/pull/6725)|

Note: Successful backport PRs will be merged automatically after passing CI.

### Questions ?
Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) and see the [Github Action logs](https://github.com/spectrocloud/librarium/actions/runs/14890796959) for details

<!--- Backport version: 9.5.1 -->
author_association: CONTRIBUTOR
user: login: vault-token-factory-spectrocloud[bot]
created_at: 2025-05-20T21:03:35Z
body: :tada: This PR is included in version 4.7.4 :tada:

The release is available on [GitHub release](https://github.com/spectrocloud/librarium/releases/tag/v4.7.4)

Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:
author_association: CONTRIBUTOR