From e153e0618611ec621304404646ce3773ecc43f29 Mon Sep 17 00:00:00 2001 From: Logan Date: Mon, 11 Mar 2019 16:10:04 +0800 Subject: [PATCH] Update _index.md --- .../v2.x/en/catalog/force-upgrade/_index.md | 16 +--------------- 1 file changed, 1 insertion(+), 15 deletions(-) diff --git a/content/rancher/v2.x/en/catalog/force-upgrade/_index.md b/content/rancher/v2.x/en/catalog/force-upgrade/_index.md index 4214c33928e..7e3597297b6 100644 --- a/content/rancher/v2.x/en/catalog/force-upgrade/_index.md +++ b/content/rancher/v2.x/en/catalog/force-upgrade/_index.md @@ -7,7 +7,7 @@ aliases: _Available as of v2.2.0_ -Force upgrade will force Rancher catalog apps to delete and recreate resources if needed during the upgrade. +In Kubernetes, some fields are designed to be immutable or cannot be updated directly. Force upgrade will force Rancher catalog apps to delete and recreate resources if needed during the upgrade. ### How to Force-upgrade Catalog Apps @@ -15,17 +15,3 @@ Force upgrade will force Rancher catalog apps to delete and recreate resources i For both upgrade and rollback, you can select the `Delete and recreate resources if needed during the upgrade` checkbox at the bottom of the catalog app details page to force-upgrade the app. ![force-upgrade.png]({{< baseurl >}}/img/rancher/catalog/force-upgrade.png) - - -### When to Use The Force-upgrade and Cautions - -In Kubernetes, some fields are designed to be immutable or cannot be updated directly, e.g. changing Service type from NodePort to ClusterIP will result in: -``` -Error: UPGRADE FAILED: Service "docker-registry" is invalid: spec.ports[0].nodePort: Forbidden: may not be used when `type` is 'ClusterIP' -``` -and `force-upgrade` will be recreating resources for immutable fields when force is applied. - ->**Cautions:** -> ->- Don't force-upgrade resources that contain persistent data, e.g. Statefulset or Deployment with Bounded PVC. -