From 5772d582ea85e50e9013be54fc70acd04eff3aa1 Mon Sep 17 00:00:00 2001 From: Gerasimos Dimitriadis Date: Sat, 18 Jan 2020 19:29:36 +0200 Subject: [PATCH] Fix typo in manifests path (#18753) --- .../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 fd8dccc92e..73878bbd9d 100644 --- a/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md +++ b/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md @@ -408,7 +408,7 @@ can be manually restored in `/var/lib/etcd`. In case external etcd is used this `kubeadm-backup-manifests` contains a backup of the static Pod manifest files for this control-plane Node. In case of a upgrade failure and if the automatic rollback does not work, the contents of this folder can be -manually restored in `/etc/kuberentes/manifests`. If for some reason there is no difference between a pre-upgrade +manually restored in `/etc/kubernetes/manifests`. If for some reason there is no difference between a pre-upgrade and post-upgrade manifest file for a certain component, a backup file for it will not be written. ## How it works