第 2 章 Performing automated in-place cluster upgrades
If you installed using the standard cluster installation process, and the inventory file that was used is available, you can use upgrade playbooks to automate the cluster upgrade process.
To upgrade OpenShift Container Platform, you run Ansible playbooks with the same inventory file that you used during installation. You run the same v3_11 upgrade playbooks to:
- Upgrade existing OpenShift Container Platform version 3.10 clusters to version 3.11.
- Upgrade OpenShift Container Platform version 3.11 clusters to the latest asynchronous errata update.
重要
Running Ansible playbooks with the --tags or --check options is not supported by Red Hat.
2.1. Upgrade workflow
The 3.10 to 3.11 control plane upgrade performs the following steps for you:
- Back up all etcd data for recovery purposes.
- Update the API and controllers from 3.10 to 3.11.
- Update internal data structures to 3.11.
- Update the default router, if one exists, from 3.10 to 3.11.
- Update the default registry, if one exists, from 3.10 to 3.11.
- Update the default image streams and InstantApp templates.
The 3.10 to 3.11 node upgrade performs a rolling update of nodes, which:
- Marks a subset of nodes unschedulable and drains them of pods.
- Updates node components from 3.10 to 3.11.
- Returns those nodes to service.
