Chapter 9. Uninstalling

Procedure

1. In the OpenShift Container Platform web console, navigate to Workloads Pods.
2. Enter the name of the pod that you want to delete in the Search by name field.
3. Click the pod name to open it.
4. On the Details page, check that kata or kata-remote is displayed for Runtime class.
5. Click the Options menu and select Delete Pod.
6. Click Delete.

Procedure

1. In the OpenShift Container Platform web console, navigate to Operators Installed Operators.
2. Enter OpenShift sandboxed containers Operator in the Search by name field.
3. Click the Operator to open it and then click the KataConfig tab.
4. Click the Options menu and select Delete KataConfig.
5. Click Delete in the confirmation window.

Procedure

1. Navigate to Operators Installed Operators.
2. Enter OpenShift sandboxed containers Operator in the Search by name field.

3. On the right side of the Operator Details page, select Uninstall Operator from the Actions list.

   An Uninstall Operator? dialog box is displayed.

4. Click Uninstall to remove the Operator, Operator deployments, and pods.
5. Navigate to Administration Namespaces.
6. Enter openshift-sandboxed-containers-operator in the Search by name field.
7. Click the Options menu and select Delete Namespace.
8. In the confirmation dialog, enter openshift-sandboxed-containers-operator and click Delete.

Procedure

1. In the web console, navigate to Administration CustomResourceDefinitions.
2. Enter the KataConfig name in the Search by name field.
3. Click the Options menu and select Delete CustomResourceDefinition.
4. Click Delete in the confirmation window.

Procedure

1. Search for the pods by running the following command:

   $ oc get pods -A -o json | jq -r '.items[] | \
     select(.spec.runtimeClassName == "<runtime>").metadata.name' 

   1

   Copy to Clipboard Toggle word wrap

   1

   Replace <runtime> with kata for bare metal deployments, or with kata-remote for AWS, Azure, IBM Z®, and IBM® LinuxONE deployments.

2. Delete each pod by running the following command:

   $ oc delete pod <pod>

   Copy to Clipboard Toggle word wrap

Procedure

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

   $ oc delete kataconfig example-kataconfig

   Copy to Clipboard Toggle word wrap

   The OpenShift sandboxed containers Operator removes all resources that were initially created to enable the runtime on your cluster.

   Important

   When you delete the KataConfig CR, the CLI stops responding until all worker nodes reboot. You must wait for the deletion process to complete before performing the verification.

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. Delete the subscription by running the following command:

   $ oc delete subscription sandboxed-containers-operator -n openshift-sandboxed-containers-operator

   Copy to Clipboard Toggle word wrap

2. Delete the namespace by running the following command:

   $ oc delete namespace openshift-sandboxed-containers-operator

   Copy to Clipboard Toggle word wrap

Procedure

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

   $ oc delete crd kataconfigs.kataconfiguration.openshift.io

   Copy to Clipboard Toggle word wrap

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

   $ oc get crd kataconfigs.kataconfiguration.openshift.io

   Copy to Clipboard Toggle word wrap

   Example output

   Unknown CRD kataconfigs.kataconfiguration.openshift.io

   Copy to Clipboard Toggle word wrap

Procedure

1. In the OpenShift Container Platform web console, navigate to Operators Installed Operators.
2. Enter Confidential compute attestation in the Search by name field.
3. Click the Operator to open it and then click the KbsConfig tab.
4. Click the Options menu and select Delete KbsConfig.
5. Click Delete in the confirmation window.

Procedure

1. Navigate to Operators Installed Operators.
2. Enter Confidential compute attestation in the Search by name field.

3. On the right side of the Operator Details page, select Uninstall Operator from the Actions list.

   An Uninstall Operator? dialog box is displayed.

4. Click Uninstall to remove the Operator, Operator deployments, and pods.
5. Navigate to Administration Namespaces.
6. Enter trustee-operator-system in the Search by name field.
7. Click the Options menu and select Delete Namespace.
8. In the confirmation dialog, enter trustee-operator-system and click Delete.

Procedure

1. In the web console, navigate to Administration CustomResourceDefinitions.
2. Enter the KbsConfig name in the Search by name field.
3. Click the Options menu and select Delete CustomResourceDefinition.
4. Click Delete in the confirmation window.

Procedure

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

   $ oc delete kbsconfig kbsconfig

   Copy to Clipboard Toggle word wrap

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

   $ oc get kbsconfig kbsconfig

   Copy to Clipboard Toggle word wrap

   Example output

   No kbsconfig instances exist

   Copy to Clipboard Toggle word wrap

Procedure

1. Delete the subscription by running the following command:

   $ oc delete subscription trustee-operator -n trustee-operator-system

   Copy to Clipboard Toggle word wrap

2. Delete the namespace by running the following command:

   $ oc delete namespace trustee-operator-system

   Copy to Clipboard Toggle word wrap

Procedure

1. Delete the KbsConfig CRD by running the following command:

   $ oc delete crd kbsconfigs.confidentialcontainers.org

   Copy to Clipboard Toggle word wrap

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

   $ oc get crd kbsconfigs.confidentialcontainers.org

   Copy to Clipboard Toggle word wrap

   Example output

   Unknown CRD kbsconfigs.confidentialcontainers.org

   Copy to Clipboard Toggle word wrap