From edd3a8c23fa87160d68dfe5d966152f6a8132410 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Tue, 30 Jul 2019 13:13:28 -0700 Subject: [PATCH] Turn sentence about ingress-nginx update into a note --- .../rancher/v2.x/en/cluster-admin/editing-clusters/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/cluster-admin/editing-clusters/_index.md b/content/rancher/v2.x/en/cluster-admin/editing-clusters/_index.md index 47050d57947..c047fb9dbdc 100644 --- a/content/rancher/v2.x/en/cluster-admin/editing-clusters/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/editing-clusters/_index.md @@ -75,7 +75,7 @@ Following an upgrade to the latest version of Rancher, you can update your exist **Result:** Kubernetes begins upgrading for the cluster. During the upgrade, your cluster is unavailable. -The `ingress-nginx` pods are set to only upgrade on delete. After upgrading your cluster, you need to delete these pods to get the correct version for your deployment. +> **Note:** The `ingress-nginx` pods are set to only upgrade on delete. After upgrading your cluster, you need to delete these pods to get the correct version for your deployment. ### Adding a Pod Security Policy