From eee4342629c6b57c30e6bb4325299a88c8eceff2 Mon Sep 17 00:00:00 2001 From: Simon Gerber Date: Wed, 26 Jun 2024 14:17:15 +0200 Subject: [PATCH] Add callouts for steps that trigger node reboots in rollout how-to for OCP --- docs/modules/ROOT/pages/how-tos/deploy-ocp.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/modules/ROOT/pages/how-tos/deploy-ocp.adoc b/docs/modules/ROOT/pages/how-tos/deploy-ocp.adoc index 4cda2d8..4c5a22f 100644 --- a/docs/modules/ROOT/pages/how-tos/deploy-ocp.adoc +++ b/docs/modules/ROOT/pages/how-tos/deploy-ocp.adoc @@ -9,6 +9,8 @@ This guide describes how to deploy cloudscale.ch CCM on an existing cluster. If not already present add the following machine config which customizes the kubelet systemd service on all cluster nodes. As described in https://github.com/openshift/infrastructure-provider-onboarding-guide/blob/main/docs/platform-external/installing.md. + +IMPORTANT: Applying the `MachineConfig` causes node reboots. ++ [source,yaml] ---- spec: @@ -93,6 +95,8 @@ worker-8e76 cloudscale://a0ba2200-bfc3-435a-b733-8607b6ee4190 . Patch infrastructure config + +IMPORTANT: This step triggers node reboots to apply the Kubelet flag `--cloud-provider=external`. ++ [source,bash] ---- kubectl --as cluster-admin patch infrastructure.config cluster --type=merge -p '{"spec":{"platformSpec":{"external":{"platformName":"cloudscale.ch"},"type":"External"}}}'