|
| 1 | +:_content-type: ASSEMBLY |
| 2 | +[id="upgrading-sandboxed-containers"] |
| 3 | += Upgrading {sandboxed-containers-first} |
| 4 | +include::_attributes/common-attributes.adoc[] |
| 5 | +:context: upgrading-sandboxed-containers |
| 6 | + |
| 7 | +toc::[] |
| 8 | + |
| 9 | +The upgrade of the {sandboxed-containers-first} components consists of the following three steps: |
| 10 | + |
| 11 | +* Upgrading {product-title} to update the `Kata` runtime and its dependencies. |
| 12 | +
|
| 13 | +* Upgrading the {sandboxed-containers-operator} to update the Operator subscription. |
| 14 | +
|
| 15 | +* Manually patching the `KataConfig` custom resource (CR) to update the monitor pods. |
| 16 | +
|
| 17 | +You can upgrade {product-title} before or after the {sandboxed-containers-operator} upgrade, with the one exception noted below. Always apply the `KataConfig` patch immediately after upgrading {sandboxed-containers-operator}. |
| 18 | + |
| 19 | +[IMPORTANT] |
| 20 | +==== |
| 21 | +
|
| 22 | +If you are upgrading to {product-title} 4.11 with {sandboxed-containers-first} 1.3, the recommended order is to first upgrade {sandboxed-containers-first} from 1.2 to 1.3, and then upgrade {product-title} from 4.10 to 4.11. |
| 23 | +==== |
| 24 | + |
| 25 | +[id="sandboxed-containers-upgrade-resources"] |
| 26 | +== Upgrading the {sandboxed-containers-first} resources |
| 27 | + |
| 28 | +The {sandboxed-containers-first} resources are deployed onto the cluster using {op-system-first} extensions. |
| 29 | + |
| 30 | +//Update the Red Hat CoreOS extension with the updated link once PR is approved for the Understanding section. |
| 31 | + |
| 32 | +The {op-system} extension `sandboxed containers` contains the required components to run Kata Containers such as the Kata containers runtime, the hypervisor QEMU, and other dependencies. You upgrade the extension by upgrading the cluster to a new release of {product-title}. |
| 33 | + |
| 34 | +For more information about upgrading {product-title}, see xref:../updating/index.adoc#index[Updating Clusters]. |
| 35 | + |
| 36 | +[id="sandboxed-containers-upgrading-operator"] |
| 37 | +== Upgrading the {sandboxed-containers-operator} |
| 38 | + |
| 39 | +Use Operator Lifecycle Manager (OLM) to upgrade the {sandboxed-containers-operator} either manually or automatically. Selecting between manual or automatic upgrade during the initial deployment determines the future upgrade mode. For manual upgrades, the web console shows the available updates that can be installed by the cluster administrator. |
| 40 | + |
| 41 | +For more information about upgrading the {sandboxed-containers-operator} in Operator Lifecycle Manager (OLM), see xref:../operators/admin/olm-upgrading-operators.adoc#olm-upgrading-operators[Upgrading installed Operators]. |
| 42 | + |
| 43 | +[id="sandboxed-containers-upgrading-monitor-pods"] |
| 44 | +== Upgrading the {sandboxed-containers-first} monitor pods |
| 45 | + |
| 46 | +After upgrading {sandboxed-containers-first}, you need to update the monitor image in the `KataConfig` CR to upgrade the monitor pods. Otherwise, the monitor pods will continue running images from the previous version. |
| 47 | + |
| 48 | +You can perform the update using the web console or the CLI. |
| 49 | + |
| 50 | +include::modules/sandboxed-containers-upgrading-monitor-pods-web.adoc[leveloffset=+2] |
| 51 | +include::modules/sandboxed-containers-upgrading-monitor-pods-cli.adoc[leveloffset=+2] |
0 commit comments