Chapter 5. Uninstall
You uninstall Red Hat build of Trustee by uninstalling the Red Hat build of Trustee Operator and deleting its resources.
You perform the following tasks:
-
Delete the
KbsConfigcustom resource. - Uninstall the Red Hat build of Trustee Operator.
-
Delete the
KbsConfigcustom resource definition.
5.1. Deleting TrusteeConfig custom resources Copy linkLink copied to clipboard!
Delete a TrusteeConfig custom resource to remove Red Hat build of Trustee configuration and all autogenerated resources.
Procedure
Delete the
TrusteeConfigcustom resource by running the following command:$ oc delete trusteeconfig <name> -n trustee-operator-systemwhere
<name>is the name of yourTrusteeConfigresource.Verify that all generated resources are removed by running the following command:
$ oc get configmaps,secrets,kbsconfig -n trustee-operator-system
Verification
-
All autogenerated config maps, secrets, and the
KbsConfigcustom resource are removed. - Trustee pods are terminated.
5.2. Uninstalling the Red Hat build of Trustee Operator Copy linkLink copied to clipboard!
You uninstall the Red Hat build of Trustee Operator by using the command line.
Procedure
Delete the subscription by running the following command:
$ oc delete subscription trustee-operatorDelete the namespace by running the following command:
$ oc delete namespace trustee-operator-system
5.3. Troubleshooting pod startup failures with NVIDIA GPU attestation Copy linkLink copied to clipboard!
If a pod with NVIDIA GPU attestation fails to start, check the pod events and logs to identify error messages.
Procedure
Check the pod events for error messages:
$ oc describe pod <pod_name>Review the pod logs:
$ oc logs <pod_name>Examine the output for attestation-related errors, such as:
- NVIDIA Remote Attestation Service (NRAS) connection failures
- Policy evaluation errors
- GPU device allocation issues
5.4. Troubleshooting NVIDIA Remote Attestation Service connection failures Copy linkLink copied to clipboard!
If Red Hat build of Trustee cannot connect to NVIDIA Remote Attestation Service (NRAS), verify network connectivity and policies.
Procedure
Test network connectivity to NVIDIA Remote Attestation Service from the Red Hat build of Trustee cluster:
$ oc exec -n trustee-operator-system deployment/trustee-deployment -- curl -I https://nras.attestation.nvidia.comThe command should return HTTP headers indicating successful connectivity.
- Verify that network policies allow outbound HTTPS connections to NVIDIA cloud services.
-
If the connection fails, review your cluster’s egress firewall rules and ensure that traffic to
nras.attestation.nvidia.comis permitted.
5.5. Troubleshooting policy evaluation failures Copy linkLink copied to clipboard!
If attestation policy evaluation fails, review the Open Policy Agent (OPA) rules and verify that NVIDIA Remote Attestation Service (NRAS) claim names match expected values.
Procedure
- Review the attestation policy OPA rules to ensure they are correctly configured for NVIDIA GPU attestation.
- Verify that the NRAS claim names in your policy match the expected values from the attestation response.
Check Red Hat build of Trustee logs for policy evaluation details:
$ oc logs -n trustee-operator-system deployment/trustee-deployment | grep -i "policy"- Review the log output for specific policy evaluation errors or mismatched claim values.
5.6. Troubleshooting GPU accessibility in containers Copy linkLink copied to clipboard!
If the GPU is not accessible within the container, verify that the NVIDIA GPU Operator is installed and GPU passthrough is configured correctly.
Procedure
Verify that the NVIDIA GPU Operator is installed on your cluster:
$ oc get pods -n nvidia-gpu-operatorCheck the worker node for GPU visibility:
$ oc debug node/<worker_node_name> -- chroot /host nvidia-smiThe command should list available GPU devices.
- Verify that GPU passthrough is configured correctly on the worker node.
- Ensure that the pod requesting the GPU has the correct resource limits specified in its configuration.