From c7cf563998b5af59592a3773b6d3daa5256e5c38 Mon Sep 17 00:00:00 2001 From: Kuni Sen Date: Mon, 22 Sep 2025 12:06:15 +0900 Subject: [PATCH 01/13] Update perform-ece-hosts-maintenance.md --- .../ece/perform-ece-hosts-maintenance.md | 66 ++++++++++++++++++- 1 file changed, 65 insertions(+), 1 deletion(-) diff --git a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md index 9a1d881e85..90b39c4100 100644 --- a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md +++ b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md @@ -20,12 +20,13 @@ These steps show how you can safely perform maintenance on hosts in your ECE ins You can perform these maintenance actions on the hosts in your ECE installation using one of these methods: * [By disabling the Docker daemon (nondestructive)](#ece-perform-host-maintenance-docker-disable) +* [By disabling the Podman related services (nondestructive)](#ece-perform-host-maintenance-podman-disable) - **For Podman Only** * [By deleting the host (destructive)](#ece-perform-host-maintenance-delete-runner) * [By shutting down the host (less destructive)](#ece-perform-host-maintenance-delete-runner) Which method you choose depends on how invasive your host maintenance needs to be. If your host maintenance could affect ECE, use the destructive method that first deletes the host from your installation. These methods include a step that moves any hosted {{es}} clusters and {{kib}} instances off the affected hosts and are generally considered safe, provided that your ECE installation still has sufficient resources available to operate after the host has been removed. -## By disabling the Docker daemon [ece-perform-host-maintenance-docker-disable] +## By disabling the Docker daemon (Non Destructive) [ece-perform-host-maintenance-docker-disable] This method lets you perform maintenance actions on hosts without first removing the associated host from your {{ece}} installation. It works by disabling the Docker daemon. The host remains a part of your ECE installation throughout these steps but will be offline and the resources it provides will not be available. @@ -71,6 +72,69 @@ To perform host maintenance: After the host shows a green status in the Cloud UI, it is fully functional again and can be used as before. +## By disabling the Podman related services (Non Destructive) [ece-perform-host-maintenance-podman-disable] + +:::{note} +This section only applies to Podman. +::: + +This method lets you perform maintenance actions on hosts without first removing the associated host from your {{ece}} installation. It works by disabling the Podman related services. The host remains a part of your ECE installation throughout these steps but will be offline and the resources it provides will not be available. + +To perform host maintenance: + +1. Recommended: If the host holds the allocator role and you have enough spare capacity: + 1. [Enable maintenance mode](enable-maintenance-mode.md) on the allocator. + 2. [Move all nodes off the allocator](move-nodes-instances-from-allocators.md) and to other allocators in your installation. Moving all nodes lets you retain the same level of redundancy for highly available {{es}} clusters and ensures that other clusters without high availability remain available. + ::::{important} + Skipping Step 1 will affect the availability of clusters with nodes on the allocator. + :::: + +2. Disable the Podman Service, Podman Socket, and Podman Restart Service + + ```sh + sudo systemctl disable podman.service + sudo systemctl disable podman.socket + sudo systemctl disable podman-restart.service + ``` + +3. Reboot the host: + + ```sh + sudo reboot + ``` + +After rebooting, confirm there are no running containers: +- `sudo podman ps` - Output should be empty + +If an `frc-*` or `fac-*` container is found to be running for some reason, stop it: +- `sudo podman stop $(sudo podman ps -a --filter "name=fac" --filter "name=frc" --format "{{.ID}}")` + +4. Perform your maintenance on the host, such as patching the operating system. +5. Re-enable the Podman related services: + + ```sh + sudo systemctl enable podman.service + sudo systemctl enable podman.socket + sudo systemctl enable podman-restart.service + ``` + +6. Reboot the host again: + + ```sh + sudo reboot + ``` + +Confirm the containers have started: +- `sudo podman ps -a` + - use `-a` flag so no containers are overlooked + + +7. If you enabled maintenance mode in Step 1: Take the allocator out of maintenance mode. +8. Optional for allocators: ECE will start using the allocator again as you create new or change existing clusters, but it will not automatically redistribute nodes to an allocator after it becomes available. If you want to move nodes back to the same allocator after host maintenance, you need to manually [move the nodes](move-nodes-instances-from-allocators.md) and specify the allocator as a target. +9. Verify that all ECE services and deployments are back up by checking that the host shows a green status in the Cloud UI. + +After the host shows a green status in the Cloud UI, it is fully functional again and can be used as before. + ## By deleting the host (destructive) [ece-perform-host-maintenance-delete-runner] This method lets you perform potentially destructive maintenance actions on hosts. It works by deleting the associated host, which removes the host from your {{ece}} installation. To add the host to your ECE installation again after host maintenance is complete, you must reinstall ECE. From 570b980438e510c6d573bdba3bfdc7da526431b7 Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Wed, 24 Sep 2025 12:01:38 +0900 Subject: [PATCH 02/13] Update deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md index 90b39c4100..c06c647e33 100644 --- a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md +++ b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md @@ -26,7 +26,7 @@ You can perform these maintenance actions on the hosts in your ECE installation Which method you choose depends on how invasive your host maintenance needs to be. If your host maintenance could affect ECE, use the destructive method that first deletes the host from your installation. These methods include a step that moves any hosted {{es}} clusters and {{kib}} instances off the affected hosts and are generally considered safe, provided that your ECE installation still has sufficient resources available to operate after the host has been removed. -## By disabling the Docker daemon (Non Destructive) [ece-perform-host-maintenance-docker-disable] +## By disabling the Docker daemon (nondestructive) [ece-perform-host-maintenance-docker-disable] This method lets you perform maintenance actions on hosts without first removing the associated host from your {{ece}} installation. It works by disabling the Docker daemon. The host remains a part of your ECE installation throughout these steps but will be offline and the resources it provides will not be available. From 32ba70402beba3c44718f64c12ef44a392d46ec0 Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Wed, 24 Sep 2025 12:01:48 +0900 Subject: [PATCH 03/13] Update deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md index c06c647e33..9443d4848d 100644 --- a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md +++ b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md @@ -72,7 +72,7 @@ To perform host maintenance: After the host shows a green status in the Cloud UI, it is fully functional again and can be used as before. -## By disabling the Podman related services (Non Destructive) [ece-perform-host-maintenance-podman-disable] +## By disabling the Podman related services (nondestructive) [ece-perform-host-maintenance-podman-disable] :::{note} This section only applies to Podman. From bd2388f2fde4248837a5beeb14576ef4a3cbd2b4 Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Wed, 24 Sep 2025 12:02:29 +0900 Subject: [PATCH 04/13] Update deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md index 9443d4848d..caff00309a 100644 --- a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md +++ b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md @@ -20,7 +20,7 @@ These steps show how you can safely perform maintenance on hosts in your ECE ins You can perform these maintenance actions on the hosts in your ECE installation using one of these methods: * [By disabling the Docker daemon (nondestructive)](#ece-perform-host-maintenance-docker-disable) -* [By disabling the Podman related services (nondestructive)](#ece-perform-host-maintenance-podman-disable) - **For Podman Only** +* [By disabling the Podman related services (nondestructive)](#ece-perform-host-maintenance-podman-disable) * [By deleting the host (destructive)](#ece-perform-host-maintenance-delete-runner) * [By shutting down the host (less destructive)](#ece-perform-host-maintenance-delete-runner) From 06873facc13f6d55320842116e0c67ca9c549f9f Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Wed, 24 Sep 2025 12:03:04 +0900 Subject: [PATCH 05/13] Update deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md index caff00309a..b3dbfadeec 100644 --- a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md +++ b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md @@ -89,7 +89,7 @@ To perform host maintenance: Skipping Step 1 will affect the availability of clusters with nodes on the allocator. :::: -2. Disable the Podman Service, Podman Socket, and Podman Restart Service +2. Disable the Podman service, Podman socket, and Podman restart service: ```sh sudo systemctl disable podman.service From baa70512cce853435820c403c662f99eb941b36e Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Wed, 24 Sep 2025 12:03:26 +0900 Subject: [PATCH 06/13] Update deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- .../ece/perform-ece-hosts-maintenance.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md index b3dbfadeec..7ac2d3b11b 100644 --- a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md +++ b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md @@ -103,11 +103,16 @@ To perform host maintenance: sudo reboot ``` -After rebooting, confirm there are no running containers: -- `sudo podman ps` - Output should be empty +4. After rebooting, confirm there are no running containers by running the following command. The output should be empty. + ```sh + sudo podman ps + ``` -If an `frc-*` or `fac-*` container is found to be running for some reason, stop it: -- `sudo podman stop $(sudo podman ps -a --filter "name=fac" --filter "name=frc" --format "{{.ID}}")` + If an `frc-*` or `fac-*` container is returned in the output, stop it: + + ```sh + sudo podman stop $(sudo podman ps -a --filter "name=fac" --filter "name=frc" --format "{{.ID}}") + ``` 4. Perform your maintenance on the host, such as patching the operating system. 5. Re-enable the Podman related services: From dee79f1557d46a0624b7f21237ea140c735b172b Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Wed, 24 Sep 2025 12:03:34 +0900 Subject: [PATCH 07/13] Update deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- .../maintenance/ece/perform-ece-hosts-maintenance.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md index 7ac2d3b11b..13ee76afb7 100644 --- a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md +++ b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md @@ -129,9 +129,13 @@ To perform host maintenance: sudo reboot ``` -Confirm the containers have started: -- `sudo podman ps -a` - - use `-a` flag so no containers are overlooked +7. Confirm the containers have started: + + ```sh + sudo podman ps -a + ``` + + The use `-a` flag ensures that no containers are overlooked. 7. If you enabled maintenance mode in Step 1: Take the allocator out of maintenance mode. From cdd26f189fdb50e0bbecda019f0abeb97d4b90f4 Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Wed, 24 Sep 2025 12:03:49 +0900 Subject: [PATCH 08/13] Update deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md index 13ee76afb7..71762c9d58 100644 --- a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md +++ b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md @@ -138,7 +138,7 @@ To perform host maintenance: The use `-a` flag ensures that no containers are overlooked. -7. If you enabled maintenance mode in Step 1: Take the allocator out of maintenance mode. +7. If you enabled maintenance mode in Step 1, take the allocator out of maintenance mode. 8. Optional for allocators: ECE will start using the allocator again as you create new or change existing clusters, but it will not automatically redistribute nodes to an allocator after it becomes available. If you want to move nodes back to the same allocator after host maintenance, you need to manually [move the nodes](move-nodes-instances-from-allocators.md) and specify the allocator as a target. 9. Verify that all ECE services and deployments are back up by checking that the host shows a green status in the Cloud UI. From 56dde2dda8df86d99f092e11a692c23673db314c Mon Sep 17 00:00:00 2001 From: Kuni Sen Date: Wed, 24 Sep 2025 12:10:51 +0900 Subject: [PATCH 09/13] Update perform-ece-hosts-maintenance.md tweaked the structure to make it nested and fixed the numbering --- .../ece/perform-ece-hosts-maintenance.md | 25 +++++++++---------- 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md index 71762c9d58..46abf633f1 100644 --- a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md +++ b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md @@ -19,14 +19,17 @@ These steps show how you can safely perform maintenance on hosts in your ECE ins You can perform these maintenance actions on the hosts in your ECE installation using one of these methods: -* [By disabling the Docker daemon (nondestructive)](#ece-perform-host-maintenance-docker-disable) -* [By disabling the Podman related services (nondestructive)](#ece-perform-host-maintenance-podman-disable) +* [By disabling the container services (nondestructive)](#ece-perform-host-maintenance-container-engine-disable): + * [For Docker-based installations: Disabling the Docker service](#ece-perform-host-maintenance-docker-disable) + * [For Podman-based installations: Disabling the Podman-related services](#ece-perform-host-maintenance-podman-disable) * [By deleting the host (destructive)](#ece-perform-host-maintenance-delete-runner) * [By shutting down the host (less destructive)](#ece-perform-host-maintenance-delete-runner) Which method you choose depends on how invasive your host maintenance needs to be. If your host maintenance could affect ECE, use the destructive method that first deletes the host from your installation. These methods include a step that moves any hosted {{es}} clusters and {{kib}} instances off the affected hosts and are generally considered safe, provided that your ECE installation still has sufficient resources available to operate after the host has been removed. -## By disabling the Docker daemon (nondestructive) [ece-perform-host-maintenance-docker-disable] +## By disabling the container services (nondestructive) [ece-perform-host-maintenance-container-engine-disable] + +### For Docker-based installations: Disabling the Docker service [ece-perform-host-maintenance-docker-disable] This method lets you perform maintenance actions on hosts without first removing the associated host from your {{ece}} installation. It works by disabling the Docker daemon. The host remains a part of your ECE installation throughout these steps but will be offline and the resources it provides will not be available. @@ -72,11 +75,7 @@ To perform host maintenance: After the host shows a green status in the Cloud UI, it is fully functional again and can be used as before. -## By disabling the Podman related services (nondestructive) [ece-perform-host-maintenance-podman-disable] - -:::{note} -This section only applies to Podman. -::: +### For Podman-based installations: Disabling the Podman-related services [ece-perform-host-maintenance-podman-disable] This method lets you perform maintenance actions on hosts without first removing the associated host from your {{ece}} installation. It works by disabling the Podman related services. The host remains a part of your ECE installation throughout these steps but will be offline and the resources it provides will not be available. @@ -134,13 +133,13 @@ To perform host maintenance: ```sh sudo podman ps -a ``` - - The use `-a` flag ensures that no containers are overlooked. + The use `-a` flag ensures that no containers are overlooked. -7. If you enabled maintenance mode in Step 1, take the allocator out of maintenance mode. -8. Optional for allocators: ECE will start using the allocator again as you create new or change existing clusters, but it will not automatically redistribute nodes to an allocator after it becomes available. If you want to move nodes back to the same allocator after host maintenance, you need to manually [move the nodes](move-nodes-instances-from-allocators.md) and specify the allocator as a target. -9. Verify that all ECE services and deployments are back up by checking that the host shows a green status in the Cloud UI. + +8. If you enabled maintenance mode in Step 1, take the allocator out of maintenance mode. +9. Optional for allocators: ECE will start using the allocator again as you create new or change existing clusters, but it will not automatically redistribute nodes to an allocator after it becomes available. If you want to move nodes back to the same allocator after host maintenance, you need to manually [move the nodes](move-nodes-instances-from-allocators.md) and specify the allocator as a target. +10. Verify that all ECE services and deployments are back up by checking that the host shows a green status in the Cloud UI. After the host shows a green status in the Cloud UI, it is fully functional again and can be used as before. From 4692a0b7720346e1f7225ef2b07a61ab5ea3f381 Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Thu, 25 Sep 2025 09:08:03 +0900 Subject: [PATCH 10/13] Update deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- .../maintenance/ece/perform-ece-hosts-maintenance.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md index 46abf633f1..7ecb2be46d 100644 --- a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md +++ b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md @@ -20,8 +20,8 @@ These steps show how you can safely perform maintenance on hosts in your ECE ins You can perform these maintenance actions on the hosts in your ECE installation using one of these methods: * [By disabling the container services (nondestructive)](#ece-perform-host-maintenance-container-engine-disable): - * [For Docker-based installations: Disabling the Docker service](#ece-perform-host-maintenance-docker-disable) - * [For Podman-based installations: Disabling the Podman-related services](#ece-perform-host-maintenance-podman-disable) + * [For Docker-based installations: disable the Docker service](#ece-perform-host-maintenance-docker-disable) + * [For Podman-based installations: disable the Podman-related services](#ece-perform-host-maintenance-podman-disable) * [By deleting the host (destructive)](#ece-perform-host-maintenance-delete-runner) * [By shutting down the host (less destructive)](#ece-perform-host-maintenance-delete-runner) From b53dc315e76e9ba57c734c9914eadb5fc4877729 Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Thu, 25 Sep 2025 09:08:35 +0900 Subject: [PATCH 11/13] Update deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md index 7ecb2be46d..e6eb1c5673 100644 --- a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md +++ b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md @@ -29,6 +29,8 @@ Which method you choose depends on how invasive your host maintenance needs to b ## By disabling the container services (nondestructive) [ece-perform-host-maintenance-container-engine-disable] +The way that you disable container services differs based on the platform you used to deploy your ECE hosts. + ### For Docker-based installations: Disabling the Docker service [ece-perform-host-maintenance-docker-disable] This method lets you perform maintenance actions on hosts without first removing the associated host from your {{ece}} installation. It works by disabling the Docker daemon. The host remains a part of your ECE installation throughout these steps but will be offline and the resources it provides will not be available. From c484136f6c5e27980ce7e845350f3beee0e7a1cb Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Thu, 25 Sep 2025 09:08:45 +0900 Subject: [PATCH 12/13] Update deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md index e6eb1c5673..1a9d8c8cfb 100644 --- a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md +++ b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md @@ -31,7 +31,7 @@ Which method you choose depends on how invasive your host maintenance needs to b The way that you disable container services differs based on the platform you used to deploy your ECE hosts. -### For Docker-based installations: Disabling the Docker service [ece-perform-host-maintenance-docker-disable] +### For Docker-based installations: disable the Docker service [ece-perform-host-maintenance-docker-disable] This method lets you perform maintenance actions on hosts without first removing the associated host from your {{ece}} installation. It works by disabling the Docker daemon. The host remains a part of your ECE installation throughout these steps but will be offline and the resources it provides will not be available. From 3696256a783f45c8c045055049fd9edd50310c8e Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Thu, 25 Sep 2025 09:08:51 +0900 Subject: [PATCH 13/13] Update deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md index 1a9d8c8cfb..e502072f05 100644 --- a/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md +++ b/deploy-manage/maintenance/ece/perform-ece-hosts-maintenance.md @@ -77,7 +77,7 @@ To perform host maintenance: After the host shows a green status in the Cloud UI, it is fully functional again and can be used as before. -### For Podman-based installations: Disabling the Podman-related services [ece-perform-host-maintenance-podman-disable] +### For Podman-based installations: disable the Podman-related services [ece-perform-host-maintenance-podman-disable] This method lets you perform maintenance actions on hosts without first removing the associated host from your {{ece}} installation. It works by disabling the Podman related services. The host remains a part of your ECE installation throughout these steps but will be offline and the resources it provides will not be available.