2.3. Preparing for an upgrade

After you satisfy the prerequisites, prepare for an automated upgrade:

Pull the latest subscription data from Red Hat Subscription Manager:
```
# subscription-manager refresh
```
If you are upgrading from OpenShift Container Platform 3.10 to 3.11:
1. Back up the files that you need if you must downgrade to OpenShift Container Platform 3.10:
  1. On master hosts, back up the following files:
    /etc/origin/master/master-config.yaml /etc/origin/master/master.env /etc/origin/master/scheduler.json
  2. On node hosts, including masters, back up the following files:
    /etc/origin/node/node-config.yaml
  3. On etcd hosts, including masters that have etcd co-located on them, back up the following file:
    /etc/etcd/etcd.conf
2. The upgrade process creates a backup of all etcd data for recovery purposes, but ensure that you have a recent etcd backup at /backup/etcd-xxxxxx/backup.db before continuing. Manual etcd backup steps are described in the Day Two Operations Guide.
  注意
  When you upgrade OpenShift Container Platform, your etcd configuration does not change. Whether you run etcd as static pods on master hosts or as a separate service on master hosts or separate hosts does not change after you upgrade.
3. Manually disable the 3.10 repository and enable the 3.11 repository on each master and node host. You must also enable the rhel-7-server-ansible-2.9-rpms repository, if it is not already enabled:
  - For cloud installations and on-premise installations on x86_64 servers, run the following command:
    # subscription-manager repos \ --disable="rhel-7-server-ose-3.10-rpms" \ --disable="rhel-7-server-ansible-2.4-rpms" \ --enable="rhel-7-server-ose-3.11-rpms" \ --enable="rhel-7-server-rpms" \ --enable="rhel-7-server-extras-rpms" \ --enable="rhel-7-server-ansible-2.9-rpms" # yum clean all
  - For on-premise installations on IBM POWER8 servers, run the following command:
    # subscription-manager repos \ --disable="rhel-7-for-power-le-ose-3.10-rpms" \ --enable="rhel-7-for-power-le-rpms" \ --enable="rhel-7-for-power-le-extras-rpms" \ --enable="rhel-7-for-power-le-optional-rpms" \ --enable="rhel-7-server-ansible-2.9-for-power-le-rpms" \ --enable="rhel-7-server-for-power-le-rhscl-rpms" \ --enable="rhel-7-for-power-le-ose-3.11-rpms" # yum clean all
  - For on-premise installations on IBM POWER9 servers, run the following command:
    # subscription-manager repos \ --disable="rhel-7-for-power-le-ose-3.10-rpms" \ --enable="rhel-7-for-power-9-rpms" \ --enable="rhel-7-for-power-9-extras-rpms" \ --enable="rhel-7-for-power-9-optional-rpms" \ --enable="rhel-7-server-ansible-2.9-for-power-9-rpms" \ --enable="rhel-7-server-for-power-9-rhscl-rpms" \ --enable="rhel-7-for-power-9-ose-3.11-rpms" # yum clean all
4. Ensure that you have the latest version of the openshift-ansible package on the host you run the upgrade playbooks on:
```
# yum update -y openshift-ansible
```
5. Prepare for the Cluster Monitoring Operator. In version 3.11, the Cluster Monitoring Operator is installed on an infrastructure node by default. If your cluster does not use infrastructure nodes:
  - Add an infrastructure node to your cluster.
  - Disable the Cluster Monitoring Operator by adding openshift_cluster_monitoring_operator_install=false to your inventory file.
  - Specify which node to install the Cluster Monitoring Operator on by marking it with the openshift_cluster_monitoring_operator_node_selector.
6. If you use the standard OpenShift Container Platform registry, prepare for the change from registry.access.redhat.com to registry.redhat.io. Complete the configuration steps in Accessing and Configuring the Red Hat Registry.
Review and update your inventory file.
1. Ensure that any manual configuration changes you made to your master or node configuration files since your last Ansible playbook run, whether that was initial installation or your most recent cluster upgrade, are in the inventory file. For any variables that are relevant to the manual changes you made, apply the equivalent appropriate changes to your inventory files before running the upgrade. Otherwise, your manual changes might be overwritten by default values during the upgrade, which could cause pods to not run properly or other cluster stability issues.
2. By default, the installer checks to see if your certificates will expire within a year and fails if they will expire within that time. To change the number of days that your certificate is valid, specify a new value for the openshift_certificate_expiry_warning_days parameter. For example, to ensure that your certificates are valid for 180 days, specify openshift_certificate_expiry_warning_days=180.
3. To skip checking if your certificates will expire, set openshift_certificate_expiry_fail_on_warn=False.
4. If you made any changes to admissionConfig settings in your master configuration files, review the openshift_master_admission_plugin_config variable in Configuring Your Inventory File. Failure to do so might cause pods to get stuck in Pending state if you had ClusterResourceOverride settings manually configured previously, as described in Configuring Masters for Overcommitment.
5. If you used the openshift_hostname parameter in versions of OpenShift Container Platform before 3.10, ensure that the openshift_kubelet_name_override parameter is still in your inventory file and set to the value of openshift_hostname that you used in previous versions.
  重要
  You must not remove the openshift_kubelet_name_override parameter from your inventory file after you upgrade.
6. If you manually manage the cluster’s /etc/origin/master/htpasswd file, add openshift_master_manage_htpasswd=false to your inventory file to prevent the upgrade process from overwriting the htpasswd file.

2.3.1. Updating policy definitions

During a cluster upgrade, and on every restart of any master, the default cluster roles are automatically reconciled to restore any missing permissions.

If you customized default cluster roles and want to ensure a role reconciliation does not modify them, protect each role from reconciliation:
```
$ oc annotate clusterrole.rbac <role_name> --overwrite rbac.authorization.kubernetes.io/autoupdate=false
```
警告
You must manually update the roles that contain this setting to include any new or required permissions after upgrading.
Generate a default bootstrap policy template file:
```
$ oc adm create-bootstrap-policy-file --filename=policy.json
```
注意
The contents of the file vary based on the OpenShift Container Platform version, but the file contains only the default policies.
Update the policy.json file to include any cluster role customizations.
Use the policy file to automatically reconcile roles and role bindings that are not reconcile protected:
```
$ oc auth reconcile -f policy.json
```

Reconcile security context constraints:

# oc adm policy reconcile-sccs \
    --additive-only=true \
    --confirm

2.3.2. Upgrade phases

You can upgrade the OpenShift Container Platform cluster in one or more phases. You can choose to upgrade all hosts in one phase by running a single Ansible playbook or upgrade the control plane, or master components, and nodes in multiple phases using separate playbooks.

注意

If your OpenShift Container Platform cluster uses GlusterFS pods, you must perform the upgrade in multiple phases. See Special Considerations When Using Containerized GlusterFS for details on how to upgrade with GlusterFS.

When upgrading in separate phases, the control plane phase includes upgrading:

Master components
Node services running on masters
Docker or CRI-O running on masters
Docker or CRI-O running on any stand-alone etcd hosts

If you upgrade only the nodes, you must first upgrade the control plane. The node phase includes upgrading:

Node services running on stand-alone nodes
Docker or CRI-O running on stand-alone nodes

Nodes that run master components are upgraded only during the control plane upgrade phase. This ensures that the node services and container engines on masters are not upgraded twice, once during the control plane phase and again during the node phase.

2.3.3. Node upgrade parameters

Whether you upgrade in a single or multiple phases, you can customize how the node portion of the upgrade progresses by passing certain Ansible variables to an upgrade playbook using the -e option.

Set the openshift_upgrade_nodes_serial variable to an integer or percentage to control how many node hosts are upgraded at the same time. The default is 1, which upgrades one node at a time.
For example, to upgrade 20 percent of the total number of detected nodes at a time, run:
```
$ ansible-playbook -i <path/to/inventory/file> \
    </path/to/upgrade/playbook> \
    -e openshift_upgrade_nodes_serial="20%"
```
Set the openshift_upgrade_nodes_label to specify that only nodes with a certain label are upgraded.
For example, to only upgrade nodes in the group1 region, two at a time:
```
$ ansible-playbook -i <path/to/inventory/file> \
    </path/to/upgrade/playbook> \
    -e openshift_upgrade_nodes_serial="2" \
    -e openshift_upgrade_nodes_label="region=group1"
```
注意
See Managing Nodes for more information about node labels.
Set the openshift_upgrade_nodes_max_fail_percentage variable to specify how many nodes can fail in each batch of upgrades. If the percentage of failed nodes exceeds your value, the playbook stops the upgrade process.
Set the openshift_upgrade_nodes_drain_timeout variable to specify the length of time to wait before marking a node as failed.
In this example, 10 nodes are upgraded at a time, the upgrade stops if more than 20 percent of the nodes fail, and a node is marked as failed if it takes more than 600 seconds to drain the node:
```
$ ansible-playbook -i <path/to/inventory/file> \
    </path/to/upgrade/playbook> \
    -e openshift_upgrade_nodes_serial=10 \
    -e openshift_upgrade_nodes_max_fail_percentage=20 \
    -e openshift_upgrade_nodes_drain_timeout=600
```

2.3.4. Ansible hooks for upgrades

When upgrading OpenShift Container Platform, you can execute custom tasks during specific operations through a system called hooks. Hooks allow cluster administrators to provide files defining tasks to execute before or after specific areas during upgrades. You can use hooks to validate or modify custom infrastructure when upgrading OpenShift Container Platform.

Because when a hook fails, the operation fail, design hooks that are idempotent, or can run multiple times and provide the same results.

2.3.4.1. Limitations

Hooks have no defined or versioned interface. They can use internal openshift-ansible variables, but there is no guarantee these variables will remain in future releases. In the future, hooks might be versioned, giving you advance warning that your hook needs to be updated to work with the latest openshift-ansible.
Hooks have no error handling, so an error in a hook halts the upgrade process. If you get an error, you must address the problem and then start the upgrade again.
You can run node upgrade hooks on only nodes, not masters. To run the hooks on masters, you must specify a master hook for those nodes.

2.3.4.2. Using hooks

You define hooks in the hosts inventory file under the OSEv3:vars section.

Each hook must point to a YAML file that defines Ansible tasks. This file is used as an include, meaning that the file cannot be a playbook, but is a set of tasks. Best practice suggests using absolute paths to the hook file to avoid any ambiguity.

Example hook definitions in an inventory file

[OSEv3:vars]
openshift_master_upgrade_pre_hook=/usr/share/custom/pre_master.yml
openshift_master_upgrade_hook=/usr/share/custom/master.yml
openshift_master_upgrade_post_hook=/usr/share/custom/post_master.yml

openshift_node_upgrade_pre_hook=/usr/share/custom/pre_node.yml
openshift_node_upgrade_hook=/usr/share/custom/node.yml
openshift_node_upgrade_post_hook=/usr/share/custom/post_node.yml

Example pre_master.yml task

---
# Trivial example forcing an operator to ack the start of an upgrade
# file=/usr/share/custom/pre_master.yml

- name: note the start of a master upgrade
  debug:
      msg: "Master upgrade of {{ inventory_hostname }} is about to start"

- name: require an operator agree to start an upgrade
  pause:
      prompt: "Hit enter to start the master upgrade"

2.3.4.3. Available upgrade hooks

表 2.1. Master Upgrade Hooks
Hook name	Description
`openshift_master_upgrade_pre_hook`	Runs before each master is upgraded. This hook runs against each master in serial. If a task must run against a different host, the task must use `delegate_to` or `local_action`.
`openshift_master_upgrade_hook`	Runs after each master is upgraded but before its service or system restart. This hook runs against each master in serial. If a task must run against a different host, the task must use `delegate_to` or `local_action`.
`openshift_master_upgrade_post_hook`	Runs after each master is upgraded and its service or system restarts. This hook runs against each master in serial. If a task must run against a different host, the task must use `delegate_to` or `local_action`.

表 2.2. Node upgrade hooks
Hook name	Description
`openshift_node_upgrade_pre_hook`	Runs before each node is upgraded. This hook runs against each node in serial. If a task must run against a different host, the task must use `delegate_to` or `local_action`.
`openshift_node_upgrade_hook`	Runs after each node is upgraded but before it is marked schedulable again. This hook runs against each node in serial. If a task must run against a different host, they task must use `delegate_to` or `local_action`.
`openshift_node_upgrade_post_hook`	Runs after each node is upgraded. It is the last node upgrade action. This hook runs against each node in serial. If a task must run against a different host, the task must use `delegate_to` or `local_action`.

2.3.5. Special considerations for upgrading OpenShift Container Platform

If your OpenShift Container Platform cluster uses a mixed environment or gcePD storage, you need to take more steps before you upgrade it.

Before you upgrade a mixed environment, such as one with Red Hat Enterprise Linux (RHEL) and RHEL Atomic Host, set values in the inventory file for both the openshift_pkg_version and openshift_image_tag parameters. Setting these values ensures that all nodes in your cluster run the same version of OpenShift Container Platform. While this is a best practice for major updates, such as from OpenShift Container Platform 2 to OpenShift Container Platform 3, setting these values are mandatory for minor version upgrades.

For example, to upgrade from OpenShift Container Platform 3.9 to OpenShift Container Platform 3.10, set the following parameters and values:

openshift_pkg_version=-3.10.16
openshift_image_tag=v3.10.16

注意

These parameters can also be present in other, non-mixed, environments.

2.3.5.1. Special considerations for large-scale upgrades

For large-scale cluster upgrades, which involve at least 10 worker nodes and thousands of projects and pods, the API object storage migration should be performed prior to running the upgrade playbooks, and then again after the upgrade has successfully completed. Otherwise, the upgrade process will fail.

Refer to the Running the pre- and post- API server model object migration outside of the upgrade window section of the Recommendations for large-scale OpenShift upgrades for further guidance.

2.3.5.2. Special considerations when using gcePD

Because the default gcePD storage provider uses an RWO (Read-Write Only) access mode, you cannot perform a rolling upgrade on the registry or scale the registry to multiple pods. Therefore, when upgrading OpenShift Container Platform, you must specify the following environment variables in your Ansible inventory file:

[OSEv3:vars]

openshift_hosted_registry_storage_provider=gcs
openshift_hosted_registry_storage_gcs_bucket=bucket01
openshift_hosted_registry_storage_gcs_keyfile=test.key
openshift_hosted_registry_storage_gcs_rootdirectory=/registry