Skip to content

Commit 4938553

Browse files
authored
version-4-1: docs: backport/version-4-1/pr-5100 (#5321)
1 parent 35273e9 commit 4938553

File tree

7 files changed

+154
-10
lines changed

7 files changed

+154
-10
lines changed

docs/docs-content/clusters/cluster-management/backup-restore/create-cluster-backup.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,9 @@ schedule a backup or initiate a backup on demand.
3737
- [On-demand Backup](#on-demand-backup)
3838

3939
<br />
40+
## Limitations
41+
42+
- Nodes in [Maintenance Mode](../maintenance-mode.md) are not included in the backup process.
4043

4144
## Schedule a Backup
4245

docs/docs-content/clusters/cluster-management/cluster-management.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -85,3 +85,6 @@ The following sections describe these capabilities in detail:
8585
individual users and clusters.
8686

8787
- [Image Swap](image-swap.md) - Learn how to use image swap capabilities with Palette.
88+
89+
- [Maintenance Mode](./maintenance-mode.md) - Turn off scheduling (cordon) and drain nodes, migrating workloads to other
90+
healthy nodes in the cluster without service disruptions.

docs/docs-content/clusters/cluster-management/compliance-scan.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,10 @@ purposes. To learn more about each scan type, refer to the following sections.
1717

1818
:::info
1919

20-
Scans may not work as expected when a node is in maintenance mode. Before scheduling a scan, we recommend you turn off
21-
maintenance mode if enabled. To verify if a node is in maintenance mode, navigate to **Clusters** > **Nodes** and check
22-
the **Health** column for a **Maintenance mode** icon. To turn off maintenance mode, click on the **three-dot Menu** in
23-
the row of the node you want to scan, and select **Turn off maintenance mode**.
20+
Scans cannot be performed when a node is in [maintenance mode](./maintenance-mode.md). To verify if a node is in
21+
maintenance mode, navigate to **Clusters** > **Nodes** and check the **Health** column for a **Maintenance mode** icon.
22+
To turn off maintenance mode, click on the **three-dot Menu** in the row of the node you want to scan, and select **Turn
23+
off maintenance mode**.
2424

2525
:::
2626

Lines changed: 136 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,136 @@
1+
---
2+
sidebar_label: "Maintenance Mode"
3+
title: "Maintenance Mode"
4+
description: "Learn how to enable and use maintenance mode to cordon and drain nodes."
5+
hide_table_of_contents: false
6+
sidebar_position: 240
7+
tags: ["clusters", "cluster management"]
8+
---
9+
10+
Similar to `kubectl` commands `cordon` and `drain`, maintenance mode allows you to temporarily disable scheduling for an
11+
active control plane or worker node. When a node is placed in maintenance mode, workloads are migrated automatically to
12+
other healthy nodes in the cluster without services being disrupted. Using maintenance mode makes it easier to perform
13+
necessary maintenance tasks, address node issues, and optimize workload distribution while maintaining the desired level
14+
of performance and availability.
15+
16+
## Prerequistes
17+
18+
- An active Palette host cluster with more than one control plane node and worker node.
19+
20+
- Alternate nodes with sufficient resources available where processes from maintenance nodes can be provisioned.
21+
22+
## Limitations
23+
24+
<!-- prettier-ignore -->
25+
- Static pods and DaemonSets are not evicted from the node when activating maintenance mode.
26+
27+
- Scans cannot be performed on the cluster when any node in the cluster is in maintenance mode.
28+
29+
- Nodes in maintenance mode are not included in the backup process, which also means they cannot be restored.
30+
31+
- Changes to add-on profiles are not applied to nodes in maintenance mode.
32+
33+
- Certain changes to infrastructure profiles, such as Kubernetes version upgrades, require nodes to be recreated,
34+
removing maintenance nodes in the process.
35+
36+
## Activate Maintenance Mode
37+
38+
<!-- prettier-ignore -->
39+
1. Log in to [Palette](https://console.spectrocloud.com).
40+
41+
2. Navigate to the left **Main Menu** and select **Clusters**.
42+
43+
3. Select the desired cluster and navigate to the **Nodes** tab of the cluster.
44+
45+
4. Beside the node that needs maintenance, select the **three-dot Menu** and **Turn on maintenance mode**.
46+
47+
5. When maintenance mode is activated, the **Health** icon changes to a set of tools, and the tooltip states
48+
**Maintenance Mode: Initiated**. When Maintenance Mode is finished, the tooltip changes to **Maintenance Mode:
49+
Complete**.
50+
51+
Palette reminds you in several locations that you have a node in maintenance mode:
52+
53+
- Beside the **Settings** drop-down while viewing your cluster.
54+
55+
- On the cluster’s **Overview** tab beneath **Health** status.
56+
57+
- On the cluster’s **Nodes** tab in the node’s **Health** column.
58+
59+
![Node in maintenance mode](/clusters_cluster-management_maintenance_mode.webp)
60+
61+
### Validate
62+
63+
1. Log in to [Palette](https://console.spectrocloud.com).
64+
65+
2. Navigate to the left **Main Menu** and select **Clusters**.
66+
67+
3. Select the cluster with maintenance mode active and download the [kubeconfig](./palette-webctl.md) file.
68+
69+
![The cluster details page with the two kubeconfig files elements highlighted](/clusters_cluster--management_kubeconfig_cluster-details-kubeconfig-files.webp)
70+
71+
4. Open a terminal window and set the environment variable `KUBECONFIG` to point to the kubeconfig file you downloaded.
72+
73+
```bash
74+
export KUBECONFIG=~/Downloads/admin.aws-maintenance-test.kubeconfig
75+
```
76+
77+
5. Confirm that the node is in a maintenance state, indicated by a `STATUS` of `SchedulingDisabled`.
78+
79+
```bash
80+
kubectl get nodes
81+
```
82+
83+
```bash hideClipboard {4}
84+
NAME STATUS ROLES AGE VERSION
85+
ip-10-0-1-174.ec2.internal Ready control-plane 177m v1.30.6
86+
ip-10-0-1-26.ec2.internal Ready <none> 174m v1.30.6
87+
ip-10-0-1-235.ec2.internal Ready,SchedulingDisabled <none> 174m v1.30.6
88+
```
89+
90+
## Disable Maintenance Mode
91+
92+
<!-- prettier-ignore -->
93+
1. Log in to [Palette](https://console.spectrocloud.com).
94+
95+
2. Navigate to the left **Main Menu** and select **Clusters**.
96+
97+
3. Select the desired cluster and navigate to the **Nodes** tab of the cluster.
98+
99+
4. Select the **three-dot Menu** beside the maintenance node and **Turn off maintenance mode**.
100+
101+
5. When maintenance mode is disabled, the **Health** icon reverts to a checkmark.
102+
103+
:::warning
104+
105+
Taking a node out of maintenance mode does not automatically rebalance workloads.
106+
107+
:::
108+
109+
### Validate
110+
111+
1. Log in to [Palette](https://console.spectrocloud.com).
112+
113+
2. Navigate to the left **Main Menu** and select **Clusters**.
114+
115+
3. Select the desired cluster and download the [kubeconfig](./palette-webctl.md) file.
116+
117+
![The cluster details page with the two kubeconfig files elements highlighted](/clusters_cluster--management_kubeconfig_cluster-details-kubeconfig-files.webp)
118+
119+
4. Open a terminal window and set the environment variable `KUBECONFIG` to point to the kubeconfig file you downloaded.
120+
121+
```bash
122+
export KUBECONFIG=~/Downloads/admin.aws-maintenance-test.kubeconfig
123+
```
124+
125+
5. Confirm that scheduling is no longer disabled for the node, indicated by a `STATUS` of `Ready`.
126+
127+
```bash
128+
kubectl get nodes
129+
```
130+
131+
```bash hideClipboard
132+
NAME STATUS ROLES AGE VERSION
133+
ip-10-0-1-174.ec2.internal Ready control-plane 177m v1.30.6
134+
ip-10-0-1-26.ec2.internal Ready <none> 174m v1.30.6
135+
ip-10-0-1-235.ec2.internal Ready <none> 174m v1.30.6
136+
```

docs/docs-content/vm-management/architecture.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ For more detailed information about the technical architecture of VMO, refer to
2323
By default, Palette VMO includes the following components:
2424

2525
- **Descheduler**. Enables VM live migration to different nodes in the node pool when the original node is in
26-
maintenance mode.
26+
[maintenance mode](../clusters/cluster-management/maintenance-mode.md).
2727

2828
- **Snapshot Controller**. Enables you to create VM snapshots. This component is automatically installed when you
2929
initiate or schedule cluster backups.

docs/docs-content/vm-management/create-manage-vm/migrate-vm-to-different-node.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -61,11 +61,11 @@ Follow the instructions below to migrate VMs to a different node.
6161

6262
## Evacuate a Host
6363

64-
Compute nodes can be placed into maintenance mode using Palette or manually using the `cordon` and `drain` commands. The
65-
`cordon` command marks the node as un-schedulable and the `drain`command evacuates all the VMs and pods from it. This
66-
process is useful in case you need to perform hardware maintenance on the node - for example to replace a disk or
67-
network interface card (NIC) card, perform memory maintenance, or if there are any issues with a particular node that
68-
need to be resolved. To learn more, check out the
64+
Compute nodes can be placed into [maintenance mode](../../clusters/cluster-management/maintenance-mode.md) using Palette
65+
or manually using the `cordon` and `drain` commands. The `cordon` command marks the node as un-schedulable and the
66+
`drain` command evacuates all the VMs and pods from it. This process is useful in case you need to perform hardware
67+
maintenance on the node - for example to replace a disk or network interface card (NIC) card, perform memory
68+
maintenance, or if there are any issues with a particular node that need to be resolved. To learn more, check out the
6969
[Safely Drain a Node](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/#use-kubectl-drain-to-remove-a-node-from-service)
7070
Kubernetes resource.
7171

@@ -173,3 +173,5 @@ You can validate evacuation completed by following the steps below.
173173
- [Persistent Volume Access Modes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes)
174174

175175
- [Safely Drain a Node](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/#use-kubectl-drain-to-remove-a-node-from-service)
176+
177+
- [Maintenance Mode](../../clusters/cluster-management/maintenance-mode.md)
Binary file not shown.

0 commit comments

Comments
 (0)