spectrocloud · Linus-SpectroCloud · Feb 10, 2026 · Feb 10, 2026 · Feb 10, 2026 · Feb 10, 2026
@@ -0,0 +1,4 @@
+{
+  "label": "Central Edge Management",
+  "position": 20
+}
@@ -11,7 +11,7 @@ tags: ["getting-started", "tutorial", "edge"]
 
 One of the first steps in deploying an Edge cluster is preparing your Edge host with all the required artifacts. The
 process of building these artifacts is called
-[EdgeForge](../../../clusters/edge/edgeforge-workflow/edgeforge-workflow.md), and it is responsible for generating the
+[EdgeForge](../../../../clusters/edge/edgeforge-workflow/edgeforge-workflow.md), and it is responsible for generating the
 installer ISO and provider image artifacts.
 
 - Installer ISO: An ISO image that installs the Palette Edge agent on the host.
@@ -20,10 +20,10 @@ installer ISO and provider image artifacts.
   Kubernetes version during cluster deployment.
 
 This tutorial teaches you how to build the artifacts required for your Edge deployment. Once built, you will be ready to
-learn how to reference them in Edge [cluster profiles](../../../profiles/profiles.md) and how they are used to install
+learn how to reference them in Edge [cluster profiles](../../../../profiles/profiles.md) and how they are used to install
 the Palette agent on hosts.
 
-![Palette Edge architecture diagram](/getting-started/getting-started_introduction-edge_edge-diagram-edgeforge.webp)
+![Palette Edge architecture diagram](../../../../../../static/assets/docs/images/getting-started/getting-started_introduction-edge_edge-diagram-edgeforge.webp)
 
 ## Prerequisites
 
@@ -39,7 +39,7 @@ To complete this tutorial, ensure the following prerequisites are in place.
 - Access to a public image registry and permissions to push images. This tutorial uses
   [Docker Hub](https://www.docker.com/products/docker-hub/) as an example. If you need to use a private registry, refer
   to the
-  [Deploy Cluster with a Private Provider Registry](../../../clusters/edge/site-deployment/deploy-custom-registries/deploy-private-registry.md)
+  [Deploy Cluster with a Private Provider Registry](../../../../clusters/edge/site-deployment/deploy-custom-registries/deploy-private-registry.md)
   guide for instructions on how to configure the credentials.
 - The following software installed on the Linux machine:
   - [Docker Engine](https://docs.docker.com/engine/install/) with
@@ -81,7 +81,7 @@ While both the `.arg` file and [user-data](./prepare-user-data.md) file are conf
 EdgeForge process, they serve different purposes. The `.arg` file is used to customize the Edge artifact build process.
 For example, you can specify the name of the installer ISO to be built, the Kubernetes distribution and version for the
 provider images, the registry to push the images to, and more. The
-[Edge Artifact Build Configurations](../../../clusters/edge/edgeforge-workflow/palette-canvos/arg.md) page contains a
+[Edge Artifact Build Configurations](../../../../clusters/edge/edgeforge-workflow/palette-canvos/arg.md) page contains a
 list of all the configurable parameters. In contrast, the `user-data` file focuses on customizing the installer ISO.
 When the Edge host boots from the installer ISO, it applies the user data configuration to the host.
 
@@ -130,7 +130,7 @@ cat .arg
 
 :::tip
 
-You can also use the [Appliance Studio](../../../deployment-modes/appliance-mode/appliance-studio.md) configuration
+You can also use the [Appliance Studio](../../../../deployment-modes/appliance-mode/appliance-studio.md) configuration
 Graphic User Interface (GUI) to help you create the `.arg` file.
 
 :::

@@ -52,7 +52,7 @@ Review the cluster profile layers and click **Next** to proceed.
 We recommend enabling the overlay network configuration when using DHCP-enabled networks to ensure stable IP addresses
 for the cluster. However, for education purposes, this tutorial does not use the overlay network. For production use or
 detailed configuration instructions, refer to the
-[Enable Overlay Network](../../../clusters/edge/networking/vxlan-overlay.md) guide.
+[Enable Overlay Network](../../../../clusters/edge/networking/vxlan-overlay.md) guide.
 
 :::
 
@@ -90,7 +90,7 @@ single-node Edge cluster with no worker pool.
 
 The following image shows the Edge host selection in the control plane pool.
 
-![A screenshot of the nodes config during cluster deployment.](/getting-started/getting-started_introduction-edge_deploy-edge-cluster_cluster-deployment-nodes.webp)
+![A screenshot of the nodes config during cluster deployment.](../../../../../../static/assets/docs/images/getting-started/getting-started_introduction-edge_deploy-edge-cluster_cluster-deployment-nodes.webp)
 
 Next, select **Remove** to delete the worker pool and click **Next** to proceed with the deployment.
 
@@ -119,12 +119,12 @@ Confirm that your cluster displays a **Running** status and is listed as **Healt
 When the Hello Universe application is deployed and ready for network traffic, Palette exposes the service URL in the
 **Services** field. Click the URL on port **:8080** to access the application's landing page.
 
-![A screenshot of the cluster's Overview tab](/getting-started/getting-started_introduction-edge_deploy-edge-cluster_cluster-overview.webp)
+![A screenshot of the cluster's Overview tab](../../../../../../static/assets/docs/images/getting-started/getting-started_introduction-edge_deploy-edge-cluster_cluster-overview.webp)
 
 Welcome to the Spacetastic astronomy education platform. Feel free to explore the pages to learn more about space. The
 statistics page offers information on visitor counts for your deployed cluster.
 
-![A screenshot of the Hello Universe application.](/getting-started/getting-started_introduction-edge_deploy-edge-cluster_hello-universe.webp)
+![A screenshot of the Hello Universe application.](../../../../../../static/assets/docs/images/getting-started/getting-started_introduction-edge_deploy-edge-cluster_hello-universe.webp)
 
 ## Clean Up
 
@@ -162,7 +162,7 @@ Locate the Edge host configured in the [Prepare Edge Host](./prepare-edge-host.m
 and select **Delete** to delete the Edge host. Confirm the deletion by clicking **OK**. This removes the Edge host from
 Palette but does not delete the underlying infrastructure.
 
-![A screenshot of the Edge Hosts page.](/getting-started/getting-started_introduction-edge_deploy-edge-cluster_delete-host.webp)
+![A screenshot of the Edge Hosts page.](../../../../../../static/assets/docs/images/getting-started/getting-started_introduction-edge_deploy-edge-cluster_delete-host.webp)
 
 <Tabs groupId="host">
 
@@ -193,7 +193,7 @@ Next, reboot the host.
 sudo reboot
 ```
 
-Refer to [Reset Host via Terminal](../../../clusters/edge/cluster-management/reset-host.md) for more information about
+Refer to [Reset Host via Terminal](../../../../clusters/edge/cluster-management/reset-host.md) for more information about
 Edge host resetting.
 
 </TabItem>
@@ -226,6 +226,6 @@ In this tutorial, you learned how to deploy a single-node Edge cluster along wit
 host, cluster profile, and artifacts prepared in earlier tutorials from this series. This deployment completes the Edge
 Getting Started tutorial series.
 
-We encourage you to check out the [Additional Capabilities](../additional-capabilities/additional-capabilities.md)
-section to explore other Palette functionalities, and the [Edge](../../../clusters/edge/edge.md) documentation section
+We encourage you to check out the [Additional Capabilities](../../additional-capabilities/additional-capabilities.md)
+section to explore other Palette functionalities, and the [Edge](../../../../clusters/edge/edge.md) documentation section
 to learn more about Palette Edge.
@@ -0,0 +1,171 @@
+---
+sidebar_label: "Create Edge Cluster Profile"
+title: "Create Edge Cluster Profile"
+description:
+  "Get started with Kubernetes at the edge. Learn how to create an Edge native cluster profile to deploy Edge Kubernetes
+  workloads."
+icon: ""
+hide_table_of_contents: false
+sidebar_position: 40
+tags: ["getting-started", "tutorial", "edge"]
+---
+
+[Cluster profiles](../../../../../docs-content/profiles/profiles.md) are declarative, full-stack models that Palette uses to provision,
+scale, and maintain Kubernetes clusters. They are composed of layers, which can be Kubernetes manifests, Helm charts, or
+packs. [Packs](../../../../registries-and-packs/registries-and-packs.md) are a collection of files and configurations
+deployed to a cluster to provide core infrastructure functionality or customize the cluster's behavior through add-on
+integrations.
+
+This tutorial teaches you how to create an Edge native cluster profile that includes the core infrastructure layers and
+a demo application that you can access on your browser. You will learn about cluster profile layers and how to reference
+the provider images that you built in the [Build Edge Artifacts](./build-edge-artifacts.md) tutorial. After creating the
+cluster profile, you will proceed to the next tutorial, where you will use the installer ISO to bootstrap the Edge
+installation on your host and use it as a node for deploying your first Edge cluster.
+
+![Palette Edge architecture diagram](../../../../../../static/assets/docs/images/getting-started/getting-started_introduction-edge_edge-diagram-profile.webp)
+
+## Prerequisites
+
+- You have completed the steps in the [Build Edge Artifacts](./build-edge-artifacts.md) tutorial, including building the
+  installer ISO and provider image, and pushing the provider image to a registry.
+- A [Palette account](https://www.spectrocloud.com/get-started) with
+  [tenant admin](../../../../../docs-content/tenant-settings/tenant-settings.md) access.
+- One available IP address on the same network as the Edge host for the MetalLB load balancer.
+
+## Create Cluster Profile
+
+Log in to [Palette](https://console.spectrocloud.com/) and select **Profiles** from the left main menu. Click **Add
+Cluster Profile** to create your cluster profile.
+
+Follow the wizard to create a new profile. In the **Basic Information** section, assign `gs-profile` as the name, and
+provide a brief profile description. Set the type as **Full** and add the tag `env:edge`. You may leave the version
+empty, but note that the version defaults to `1.0.0` if not specified. Click **Next** to continue.
+
+The **Cloud Type** section allows you to choose the infrastructure provider for the cluster. Select **Edge Native** and
+click **Next**.
+
+The **Profile Layers** section defines the packs that compose the profile.
+
+Add the **BYOS Edge OS** pack to the OS layer. This pack enables you to use the custom image you built in the
+[Build Edge Artifacts](./build-edge-artifacts.md) tutorial as the operating system for the cluster nodes.
+
+| **Pack Name** | **Version** | **Registry**     | **Layer**        |
+| ------------- | ----------- | ---------------- | ---------------- |
+| BYOS Edge OS  | 2.1.0       | Palette Registry | Operating System |
+
+Under **Pack Details**, select **Values** to open the YAML editor. Replace the default layer manifest with the custom
+manifest generated in the [Build Edge Artifacts](./build-edge-artifacts.md) tutorial. This makes the cluster pull the
+provider images from the image registry specified in the [Build Edge Artifacts](./build-edge-artifacts.md) tutorial
+during deployment.
+
+Alternatively, if you no longer have access to the manifest, you can manually fill in the `options.system.uri` parameter
+with the address of the provider image you pushed to the registry. For example, the address used in this tutorial is
+`spectrocloud/ubuntu:k3s-1.32.3-v4.6.24-gs-tutorial`.
+
+The following image displays the OS layer with the custom manifest and registry credentials.
+
+![A screenshot of the cluster profile creation step with the OS layer.](../../../../../../static/assets/docs/images/getting-started/getting-started_introduction-edge_edge-cluster-profile_byos-cluster-profile.webp)
+
+Click **Next Layer** to continue. Add the following Kubernetes layer to your cluster profile. Ensure the Kubernetes
+version matches the version used in the provider images.
+
+| **Pack Name**         | **Version** | **Registry**     | **Layer**  |
+| --------------------- | ----------- | ---------------- | ---------- |
+| Palette Optimized K3s | 1.32.3      | Palette Registry | Kubernetes |
+
+Under **Pack Details**, select **Values** and replace the predefined `cluster-cidr` and `service-cidr` IP CIDRs if they
+overlap with the host network. For example, you can set `cluster-cidr` to `"100.64.0.0/18"` and `service-cidr` to
+`"100.64.64.0/18"`. This prevents any routing conflicts in the internal pod networking.
+
+![A screenshot of the cluster profile creation step with the Kubernetes layer.](../../../../../../static/assets/docs/images/getting-started/getting-started_introduction-edge_edge-cluster-profile_cluster-profile-k8s.webp)
+
+Click **Next Layer** to add the network layer. This tutorial uses Cilium as the example network layer.
+
+| **Pack Name** | **Version** | **Registry**     | **Layer** |
+| ------------- | ----------- | ---------------- | --------- |
+| Cilium        | 1.17.1      | Palette Registry | Network   |
+
+Click **Confirm** once you have completed adding all core layers.
+
+:::info
+
+The Edge cluster profile's core infrastructure layers do not include a Container Storage Interface (CSI) layer by
+default. If your application requires persistent storage, you must include a CSI pack. This tutorial's scope does not
+include a CSI pack.
+
+:::
+
+Next, click **Add New Pack** to include the add-on layers. Search for `MetalLB` and add the following pack to your
+cluster profile.
+
+| **Pack Name**  | **Version** | **Registry**     | **Layer**     |
+| -------------- | ----------- | ---------------- | ------------- |
+| MetalLB (Helm) | 0.14.9      | Palette Registry | Load Balancer |
+
+The MetalLB pack implements a load balancer for your Edge Kubernetes cluster. It is required to help the `LoadBalancer`
+service specified in the Hello Universe pack obtain an IP address so that you can access the demo application from your
+browser.
+
+Under **Pack Details**, select **Values** and replace the default `192.168.10.0/24` IP CIDR listed under the `addresses`
+field with a valid IP address or IP range from the host network. Click **Confirm & Create** to add the MetalLB pack to
+your cluster profile.
+
+![A screenshot of the cluster profile creation step with the MetalLB layer.](../../../../../../static/assets/docs/images/getting-started/getting-started_introduction-edge_edge-cluster-profile_profile-metallb.webp)
+
+Finally, click **Add New Pack** again and search for the Hello Universe pack.
+
+| **Pack Name**  | **Version** | **Registry**               | **Layer**   |
+| -------------- | ----------- | -------------------------- | ----------- |
+| Hello Universe | 1.3.0       | Palette Community Registry | Application |
+
+Once you select the pack, Palette displays its README file, providing additional guidance on usage and configuration
+options. This pack deploys the [hello-universe](https://github.com/spectrocloud/hello-universe) demo application.
+
+Under **Pack Details**, select **Values**, then choose **Presets**. This pack has two presets available:
+
+1. **Disable Hello Universe API** configures the `hello-universe` application as a standalone frontend application. This
+   is the default option.
+2. **Enable Hello Universe API** configures the `hello-universe` application as a three-tier application with a
+   frontend, API server, and Postgres database.
+
+Select the **Enable Hello Universe API** preset. The pack manifest changes according to this selection.
+
+When using this preset, you must provide two base64-encoded values: one for the authorization token and one for the
+database password. Replace the database password value with your own encoded value.
+
+:::tip
+
+You can use the `base64` command to create a base64-encoded value.
+
+```shell
+echo -n "password" | base64
+```
+
+The output contains your base64-encoded value.
+
+```text hideClipboard
+cGFzc3dvcmQ=
+```
+
+:::
+
+For the token, use the default encoded value listed in the
+[hello-universe](https://github.com/spectrocloud/hello-universe?tab=readme-ov-file#single-load-balancer) repository.
+
+```shell title="Example of Authentication Values"
+dbPassword: "cGFzc3dvcmQ="
+authToken: "OTMxQTNCMDItOERDQy01NDNGLUExQjItNjk0MjNEMUEwQjk0"
+```
+
+![A screenshot of the cluster profile creation step with the Hello Universe layer.](../../../../../../static/assets/docs/images/getting-started/getting-started_introduction-edge_edge-cluster-profile_cluster-profile-hellouni.webp)
+
+Click **Confirm & Create** to save the alterations and add the pack to your cluster profile.
+
+Click **Next** to proceed. If there are no compatibility issues, Palette displays the cluster profile for review. Verify
+that the layers you added are correct, and click **Finish Configuration** to create the cluster profile.
+
+## Next Steps
+
+In this tutorial, you learned how to create a cluster profile for your Edge deployment. We recommend proceeding to the
+[Prepare Edge Host](./prepare-edge-host.md) tutorial to learn how to prepare your virtual or physical device to become a
+node of an Edge cluster.
@@ -12,7 +12,7 @@ This section gives you an overview of how to get started with Palette Edge. You
 deployment of Kubernetes clusters at the edge, along with all the steps required to deploy your first Edge cluster, such
 as building the necessary artifacts and preparing the host.
 
-![Palette Getting Started Roadmap](/getting-started/getting-started_introduction-edge_roadmap.webp)
+![Palette Getting Started Roadmap](../../../../../../static/assets/docs/images/getting-started/getting-started_introduction-edge_roadmap.webp)
 
 Explore the following tutorials to learn how to deploy your first connected Edge cluster with Palette. Each tutorial is
 designed to guide you step-by-step, building on the concepts introduced in the previous one.