Chapter 11. Upgrading

Procedure

1. Delete the KataConfig CR by running the following command:

   $ oc delete kataconfig example-kataconfig

   Copy to Clipboard Toggle word wrap

2. Verify that the custom resource was deleted by running the following command:

   $ oc get kataconfig example-kataconfig

   Copy to Clipboard Toggle word wrap

   Example output

   No example-kataconfig instances exist

   Copy to Clipboard Toggle word wrap

Procedure

1. Obtain the config map you created for the peer pods:

   $ oc get cm -n openshift-sandboxed-containers-operator peer-pods-cm -o jsonpath="{.data.AZURE_IMAGE_ID}"

   Copy to Clipboard Toggle word wrap

   Use PODVM_AMI_ID for AWS. Use AZURE_IMAGE_ID for Azure.

2. Check the status stanza of the YAML file.
3. If the PODVM_AMI_ID parameter for AWS or the AZURE_IMAGE_ID parameter for Azure contains a value, set the value to "".

4. If you have set the value to "", patch the peer pods config map:

   $ oc patch configmap peer-pods-cm -n openshift-sandboxed-containers-operator -p '{"data":{"AZURE_IMAGE_ID":""}}'

   Copy to Clipboard Toggle word wrap

   Use PODVM_AMI_ID for AWS. Use AZURE_IMAGE_ID for Azure.

Procedure

1. Create an example-kataconfig.yaml manifest file according to the following example:

   apiVersion: kataconfiguration.openshift.io/v1
   kind: KataConfig
   metadata:
     name: example-kataconfig
   spec:
     enablePeerPods: true
     logLevel: info
   #  kataConfigPoolSelector:
   #    matchLabels:
   #      <label_key>: '<label_value>' 

   1

   Copy to Clipboard Toggle word wrap

2. Create the KataConfig CR by running the following command:

   $ oc apply -f example-kataconfig.yaml

   Copy to Clipboard Toggle word wrap

   The new KataConfig CR is created and installs kata-remote as a runtime class on the worker nodes.

   Wait for the kata-remote installation to complete and the worker nodes to reboot before verifying the installation.

3. Monitor the installation progress by running the following command:

   $ watch "oc describe kataconfig | sed -n /^Status:/,/^Events/p"

   Copy to Clipboard Toggle word wrap

   When the status of all workers under kataNodes is installed and the condition InProgress is False without specifying a reason, the kata-remote is installed on the cluster.

4. Verify the daemon set by running the following command:

   $ oc get -n openshift-sandboxed-containers-operator ds/osc-caa-ds

   Copy to Clipboard Toggle word wrap

5. Verify the runtime classes by running the following command:

   $ oc get runtimeclass

   Copy to Clipboard Toggle word wrap

   Example output

   NAME             HANDLER          AGE
   kata             kata             152m
   kata-remote      kata-remote      152m

   Copy to Clipboard Toggle word wrap