×

Understanding the OpenShift Update Service

Understanding the OpenShift Update Service: For clusters with internet accessibility, Red Hat provides over-the-air updates through an OKD update service as a hosted service located behind public APIs. For more information, see the following information:

Installing and configuring the OpenShift Update Service

Installing and configuring the OpenShift Update Service: Clusters with internet accessibility can access public APIs; clusters in a restricted network are unable to access public APIs for update information. To provide a similar upgrade experience in a restricted network, you can install and configure the OpenShift Update Service locally so that it is available within a disconnected environment. For more information, see the following actions:

Upgrade channels and releases

Upgrade channels and releases: Upgrade channels allow you to choose an upgrade strategy. Upgrade channels are connected to a minor version of OKD. Upgrade channels control only release selection and do not impact the version of the cluster that you install; the openshift-install binary file for a specific version of OKD always installs that version. For more information, see the following information:

Updating a cluster within a minor version using the web console

Updating a cluster within a minor version using the web console: You can update an OKD cluster by using the web console. You can update a cluster between minor versions. For more information, see the following:

Updating a cluster within a minor version using the command-line interface (CLI)

Updating a cluster within a minor version using the CLI: You can update an OKD cluster by using the oc. You can update a cluster between minor versions. For more information, see the following actions:

Performing a canary rollout update

Performing a canary rollout update: By controlling rollout of an update to the worker nodes, you can ensure that mission-critical applications stay available during the whole update, even if the update process causes your applications to fail. Depending on your organizational needs, you might want to update a small subset of worker nodes, evaluate cluster and workload health over a period of time, and then update the remaining nodes. This is referred to as a canary update. Alternatively, you might also want to fit worker node updates, which often requires a host reboot, into smaller defined maintenance windows when it is not possible to take a large maintenance window to update the entire cluster at one time. You can perform the following actions:

Updating a cluster that includes Fedora compute machines

Updating a cluster that includes Fedora compute machines: You can update an OKD cluster. If your cluster contains Fedora machines, you must update those machines. You can perform the following actions:

Updating a restricted network cluster