Skip to content

Add callouts for steps that trigger node reboots in rollout how-to for OCP #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
simu merged 1 commit into from
Jun 26, 2024
Merged

Add callouts for steps that trigger node reboots in rollout how-to for OCP #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/modules/ROOT/pages/how-tos/deploy-ocp.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down Expand Up @@ -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"}}}'
Expand Down