You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docs-content/tutorials/getting-started/palette-edge/introduction-edge.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ how you can leverage Palette Edge.
41
41
## Architecture
42
42
43
43
Each Edge cluster consists of one or more nodes, with each node representing an individual Edge host. The Edge
44
-
configuration begins with the [EdgeForge](../../../clusters/edge/edgeforge-workflow/edgeforge-workflow.md) process,
44
+
configuration begins with the [EdgeForge](../../../../docs-content/clusters/edge/edgeforge-workflow/edgeforge-workflow.md) process,
45
45
which builds two key artifacts:
46
46
47
47
1.**Installer ISO**: A bootable ISO image that includes the required dependencies, such as the Palette Agent, and
@@ -61,5 +61,5 @@ which does not require a connection to Palette.
61
61
## Next Steps
62
62
63
63
On this page, you became familiar with Palette Edge, its core capabilities, and architecture. Continue to the
64
-
[Prepare User Data](./prepare-user-data.md) tutorial to learn how to create a user data file, which is required for your
64
+
by choose whether you are going to deploy [Central Edge Management](./central-management/palette-edge.md) or [Local Edge Management](./local-management/palette-edge.md) tutorial to learn how to create a user data file, which is required for your
@@ -90,7 +90,7 @@ single-node Edge cluster with no worker pool.
90
90
91
91
The following image shows the Edge host selection in the control plane pool.
92
92
93
-

93
+

94
94
95
95
Next, select **Remove** to delete the worker pool and click **Next** to proceed with the deployment.
96
96
@@ -119,12 +119,12 @@ Confirm that your cluster displays a **Running** status and is listed as **Healt
119
119
When the Hello Universe application is deployed and ready for network traffic, Palette exposes the service URL in the
120
120
**Services** field. Click the URL on port **:8080** to access the application's landing page.
121
121
122
-

122
+

123
123
124
124
Welcome to the Spacetastic astronomy education platform. Feel free to explore the pages to learn more about space. The
125
125
statistics page offers information on visitor counts for your deployed cluster.
126
126
127
-

127
+

128
128
129
129
## Clean Up
130
130
@@ -162,7 +162,7 @@ Locate the Edge host configured in the [Prepare Edge Host](./prepare-edge-host.m
162
162
and select **Delete** to delete the Edge host. Confirm the deletion by clicking **OK**. This removes the Edge host from
163
163
Palette but does not delete the underlying infrastructure.
164
164
165
-

165
+

166
166
167
167
<TabsgroupId="host">
168
168
@@ -193,7 +193,7 @@ Next, reboot the host.
193
193
sudo reboot
194
194
```
195
195
196
-
Refer to [Reset Host via Terminal](../../../clusters/edge/cluster-management/reset-host.md) for more information about
196
+
Refer to [Reset Host via Terminal](../../../../clusters/edge/cluster-management/reset-host.md) for more information about
197
197
Edge host resetting.
198
198
199
199
</TabItem>
@@ -226,6 +226,6 @@ In this tutorial, you learned how to deploy a single-node Edge cluster along wit
226
226
host, cluster profile, and artifacts prepared in earlier tutorials from this series. This deployment completes the Edge
227
227
Getting Started tutorial series.
228
228
229
-
We encourage you to check out the [Additional Capabilities](../additional-capabilities/additional-capabilities.md)
230
-
section to explore other Palette functionalities, and the [Edge](../../../clusters/edge/edge.md) documentation section
229
+
We encourage you to check out the [Additional Capabilities](../../additional-capabilities/additional-capabilities.md)
230
+
section to explore other Palette functionalities, and the [Edge](../../../../clusters/edge/edge.md) documentation section
- One available IP address on the same network as the Edge host for the MetalLB load balancer.
34
34
35
35
## Create Cluster Profile
@@ -64,7 +64,7 @@ with the address of the provider image you pushed to the registry. For example,
64
64
65
65
The following image displays the OS layer with the custom manifest and registry credentials.
66
66
67
-

67
+

68
68
69
69
Click **Next Layer** to continue. Add the following Kubernetes layer to your cluster profile. Ensure the Kubernetes
70
70
version matches the version used in the provider images.
@@ -77,7 +77,7 @@ Under **Pack Details**, select **Values** and replace the predefined `cluster-ci
77
77
overlap with the host network. For example, you can set `cluster-cidr` to `"100.64.0.0/18"` and `service-cidr` to
78
78
`"100.64.64.0/18"`. This prevents any routing conflicts in the internal pod networking.
79
79
80
-

80
+

81
81
82
82
Click **Next Layer** to add the network layer. This tutorial uses Cilium as the example network layer.
83
83
@@ -110,7 +110,7 @@ Under **Pack Details**, select **Values** and replace the default `192.168.10.0/
110
110
field with a valid IP address or IP range from the host network. Click **Confirm & Create** to add the MetalLB pack to
111
111
your cluster profile.
112
112
113
-

113
+

114
114
115
115
Finally, click **Add New Pack** again and search for the Hello Universe pack.

160
+

161
161
162
162
Click **Confirm & Create** to save the alterations and add the pack to your cluster profile.
0 commit comments