From 6d845b5f0cf3e865f5e6f0742a4a0bc8a930a109 Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Mon, 18 Nov 2019 01:39:41 +0000 Subject: [PATCH] Clean up sample output for kubeadm upgrade (#17592) --- .../tasks/administer-cluster/kubeadm/kubeadm-upgrade.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md b/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md index fb5f47715b..e8b6ae88aa 100644 --- a/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md +++ b/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md @@ -102,7 +102,7 @@ The upgrade workflow at high level is the following: You should see output similar to this: - ```shell + ``` [upgrade/config] Making sure the configuration is correct: [upgrade/config] Reading configuration from the cluster... [upgrade/config] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml' @@ -151,7 +151,7 @@ The upgrade workflow at high level is the following: You should see output similar to this: - ```shell + ``` [preflight] Running pre-flight checks. [upgrade] Making sure the cluster is healthy: [upgrade/config] Making sure the configuration is correct: @@ -314,7 +314,7 @@ without compromising the minimum required capacity for running your workloads. You should see output similar to this: - ```shell + ``` node/ip-172-31-85-18 cordoned WARNING: ignoring DaemonSet-managed Pods: kube-system/kube-proxy-dj7d7, kube-system/weave-net-z65qx node/ip-172-31-85-18 drained