From 50e80b0f0f3b1f2a9e04ea883d3df090688f8a3e Mon Sep 17 00:00:00 2001
From: Marc Bihlmaier <30314040+rdxmb@users.noreply.github.com>
Date: Wed, 13 Nov 2019 02:12:11 +0100
Subject: [PATCH] Update kubeadm-upgrade.md (#17310)

[BUGFIX] add fix missing command
---
 .../en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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 43cb73a31dc25..fb5f47715b454 100644
--- a/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md
+++ b/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md
@@ -376,7 +376,7 @@ The `STATUS` column should show `Ready` for all your nodes, and the version numb
 If `kubeadm upgrade` fails and does not roll back, for example because of an unexpected shutdown during execution, you can run `kubeadm upgrade` again.
 This command is idempotent and eventually makes sure that the actual state is the desired state you declare.
 
-To recover from a bad state, you can also run `kubeadm upgrade --force` without changing the version that your cluster is running.
+To recover from a bad state, you can also run `kubeadm upgrade apply --force` without changing the version that your cluster is running.
 
 ## How it works