public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-22 12:55:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update _index.md

Browse Source
This commit is contained in:
Logan
2019-03-11 16:10:04 +08:00
committed by Denise Schannon
parent d66ca3af22
commit e153e06186
1 changed files with 1 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/catalog/force-upgrade/_index.md
+1 -15
View File
@@ -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.