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: .github/workflows/url-checks.yaml
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
# This workflow scans the markdown files in the repository for broken URLs.
2
2
# Additional logic is added to the Make command verify-rate-limited-links-ci to check for rate-limited URLs, including guidance on what domains to ignore.
3
-
# The workflow is scheduled to run every Monday at 6 am.
3
+
# The workflow is scheduled to run every Monday at 2PM UTC.
|**AwsSecretPartition**| Configure [AWS Secret Cloud](https://aws.amazon.com/federal/secret-cloud/) and [AWS Top Secret Cloud](https://aws.amazon.com/federal/top-secret-cloud/) accounts and deploy EKS clusters in AWS Secret and Top Secret clouds. Refer to our [Register and Manage AWS Accounts](/clusters/public-cloud/aws/add-aws-accounts) guide for more information. |:x:|:white_check_mark:|
19
19
|**AzureUSSecretCloud**| Configure [Azure Government Secret cloud](https://azure.microsoft.com/en-us/explore/global-infrastructure/government/national-security) accounts and deploy Azure IaaS clusters in Azure Government Secret cloud. Refer to our [Register and Manage Azure Accounts](/clusters/public-cloud/azure/azure-cloud/#azure-government-secret-cloud) guide for more information. |:x:|:white_check_mark:|
20
-
|**LxdMaas**| Spawn multiple control plane nodes as LXD VMs and consolidate them on MAAS-managed servers while your worker nodes run on bare metal devices. Refer to our [Create and Manage MAAS Clusters Using LXD VMs](/clusters/data-center/maas/create-manage-maas-lxd-clusters/)/> guide for more information. |:white_check_mark:|:white_check_mark:|
20
+
|**LxdMaas**| Spawn multiple control plane nodes as LXD VMs and consolidate them on MAAS-managed servers while your worker nodes run on bare metal devices. Refer to our [Create and Manage MAAS Clusters Using LXD VMs](/clusters/data-center/maas/create-manage-maas-lxd-clusters/) guide for more information. |:white_check_mark:|:white_check_mark:|
21
21
|**ApacheCloudStack**| Allows for the creation of workloads on Apache CloudStack. Refer to our [Create and Manage Apache CloudStack Clusters](/clusters/data-center/cloudstack/create-manage-cloudstack-clusters/) guide for more information. |:white_check_mark:|:white_check_mark:|
4. Restart the nodes to start the installation process.
22
22
23
-
5. Once the nodes have rebooted and entered the GRand Unified Bootloader (GRUB) menu, select the **Palette eXtended Kubernetes Edge Install (manual)** option and press **ENTER**.
23
+
5. Once the nodes have rebooted and entered the GRand Unified Bootloader (GRUB) menu, allow {props.version} to select the **Palette Edge Interactive Installer**boot option automatically.
24
24
25
-
:::caution
25
+
6. Once the **Palette Edge Interactive Installer** window appears, select the target disk for installation.
26
26
27
-
Ensure that you select the option within the first five seconds of the GRUB menu appearing, as it will automatically proceed with the default installation option after this time.
27
+
7. Choose the post-installation action: **nothing**, **reboot**, or **poweroff**, then press **ENTER**.
28
28
29
-
:::
29
+
8. Review the **Installation Summary**.
30
30
31
-
6. Once the nodes have finished booting, in the terminal, issue the following command to list the block devices.
31
+
9. Press **ENTER**to start the installation.
32
32
33
-
```bash
34
-
lsblk --paths
35
-
```
33
+
10. Wait for the installation process to complete. This will take at least 15 minutes, depending on the resources
34
+
available on the nodes. If you selected the **reboot** option in step 7, the nodes will reboot and display the Palette TUI after completion. If you chose the **poweroff** action in step 7, power on the nodes.
36
35
37
-
Use the output to identify the device name to use for the {props.version} ISO stack. For example, `/dev/sda`.
38
-
39
-
```shell hideClipboard title="Example output" {3}
40
-
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
41
-
/dev/loop0 7:0 0 1G 1 loop /run/rootfsbase
42
-
/dev/sda 8:0 0 250G 0 disk
43
-
/dev/sdb 8:16 0 5000G 0 disk
44
-
/dev/sr0 11:0 1 17.3G 0 rom /run/initramfs/live
45
-
```
46
-
47
-
7. If there are any partitions on the device you plan to use for the installation, you must delete them before proceeding. For example, if the device is `/dev/sda`, issue the following command to delete all partitions on the device.
48
-
49
-
```bash
50
-
wipefs --all /dev/sda
51
-
```
52
-
53
-
:::danger
54
-
55
-
Deleting partitions will erase all data on the device. Ensure that you back up any important data before proceeding.
56
-
57
-
:::
58
-
59
-
8. Issue the following command to edit the installation manifest.
60
-
61
-
```bash
62
-
vi /oem/stylus_config.yaml
63
-
```
64
-
65
-
9. Add the following `install.device` section to your manifest, replacing `<storage-drive>` with the device name identified in step 6.
19. Ensure you complete the configuration on each node before proceeding to the next step.
84
+
17. Ensure you complete the configuration on each node before proceeding to the next step.
140
85
141
-
20. Decide on the host that you plan to use as the leader of the group. Refer to <VersionedLinktext="Link Hosts"url="/clusters/edge/local-ui/cluster-management/link-hosts#leader-hosts"/> for more information about leader hosts.
86
+
18. Decide on the host that you plan to use as the leader of the group. Refer to <VersionedLinktext="Link Hosts"url="/clusters/edge/local-ui/cluster-management/link-hosts#leader-hosts"/> for more information about leader hosts.
142
87
143
-
21. Access the Local UI of the leader host. Local UI is used to manage the {props.version} nodes and perform administrative
88
+
19. Access the Local UI of the leader host. Local UI is used to manage the {props.version} nodes and perform administrative
144
89
tasks. It provides a web-based interface for managing the {props.version} management cluster.
145
90
146
91
In your web browser, go to `https://<node-ip>:5080`. Replace `<node-ip>` with the IP address of your node. If you
is because Local UI uses a self-signed certificate. You can safely ignore this warning and proceed to Local
152
97
UI.
153
98
154
-
22. Log in to Local UI using the credentials you provided in step 10.
99
+
20. Log in to Local UI using the credentials you provided in step 11.
155
100
156
-
23. (Optional) If you need to configure a HTTP proxy server for the node, follow the steps in the <VersionedLinktext="Configure HTTP-Proxy in Local UI"url="/clusters/edge/local-ui/host-management/configure-proxy"/> guide. When done, proceed to the next step.
101
+
21. (Optional) If you need to configure a HTTP proxy server for the node, follow the steps in the <VersionedLinktext="Configure HTTP-Proxy in Local UI"url="/clusters/edge/local-ui/host-management/configure-proxy"/> guide. When done, proceed to the next step.
157
102
158
-
24. From the left main menu, click **Linked Edge Hosts**.
103
+
22. From the left main menu, click **Linked Edge Hosts**.
159
104
160
-
25. Click **Generate token**. The host begins generating tokens that you will use to link this host with other
105
+
23. Click **Generate token**. The host begins generating tokens that you will use to link this host with other
161
106
hosts. The Base64 encoded token contains the IP address of the host, as well as an OTP that will expire in two
162
107
minutes. Once a token expires, the leader generates another token automatically.
163
108
164
-
26. Click the **Copy** button to copy the token.
109
+
24. Click the **Copy** button to copy the token.
165
110
166
-
27. Log in to Local UI on the host that you want to link to the leader host.
111
+
25. Log in to Local UI on the host that you want to link to the leader host.
167
112
168
-
28. From the left main menu, click **Linked Edge Hosts**.
113
+
26. From the left main menu, click **Linked Edge Hosts**.
169
114
170
-
29. Click **Link this device to another**.
115
+
27. Click **Link this device to another**.
171
116
172
-
30. In the pop-up box that appears, enter the token you copied from the leader host.
117
+
28. In the pop-up box that appears, enter the token you copied from the leader host.
173
118
174
-
31. Click **Confirm**.
119
+
29. Click **Confirm**.
175
120
176
-
32. Repeat steps 27-31 for every host you want to link to the leader host.
121
+
30. Repeat steps 25-29 for every host you want to link to the leader host.
177
122
178
-
33. Confirm that all linked hosts appear in the **Linked Edge Hosts** table. The following columns should show the
123
+
31. Confirm that all linked hosts appear in the **Linked Edge Hosts** table. The following columns should show the
|**Root Domain (Optional)**| The root domain for the registry. The default is set for the internal Zot registry, which is a virtual IP address assigned by [kube-vip](https://kube-vip.io/). If using an external registry, adjust this to the appropriate domain. | String |**`{{.spectro.system.cluster.kubevip}}`**|
228
173
|**Mongo Replicas**| The number of MongoDB replicas to create for the cluster. The accepted values are `1` or `3`. We recommend using **3** to provide high availability for the MongoDB database. _This value must match the **CSI Placement Count** value._| Integer |**`3`**|
229
174
230
-
39. Click **Next** when you are done.
175
+
37. Click **Next** when you are done.
231
176
232
-
40. In **Cluster Config**, configure the following options.
177
+
38. In **Cluster Config**, configure the following options.
|**NIC Name**| The name of the network interface card (NIC) to use for the nodes. Leave on **Auto** to let the system choose the appropriate NIC, or select one manually from the drop-down menu. | N/A |**Auto**|
291
236
|**Host Name (Optional)**| The hostname for the nodes. This is used to identify the nodes in the cluster. A generated hostname is provided automatically, which you can adjust to your requirements. | String |**`edge-*`**|
292
237
293
-
42. Click **Next** when you are done.
238
+
40. Click **Next** when you are done.
294
239
295
-
43. In **Review**, check that your configuration is correct. If you need to make changes, click on any of the sections
240
+
41. In **Review**, check that your configuration is correct. If you need to make changes, click on any of the sections
296
241
in the left sidebar to go back and edit the configuration.
297
242
298
243
When you are satisfied with your configuration, click **Deploy Cluster**. This will start the cluster creation
0 commit comments