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:

  1. Delete the KbsConfig custom resource.
  2. Uninstall the Red Hat build of Trustee Operator.
  3. Delete the KbsConfig custom resource definition.

5.1. Deleting TrusteeConfig custom resources

Delete a TrusteeConfig custom resource to remove Red Hat build of Trustee configuration and all autogenerated resources.

Procedure

  1. Delete the TrusteeConfig custom resource by running the following command:

    $ oc delete trusteeconfig <name> -n trustee-operator-system

    where <name> is the name of your TrusteeConfig resource.

  2. 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 KbsConfig custom resource are removed.
  • Trustee pods are terminated.

You uninstall the Red Hat build of Trustee Operator by using the command line.

Procedure

  1. Delete the subscription by running the following command:

    $ oc delete subscription trustee-operator
  2. Delete the namespace by running the following command:

    $ oc delete namespace trustee-operator-system

If a pod with NVIDIA GPU attestation fails to start, check the pod events and logs to identify error messages.

Procedure

  1. Check the pod events for error messages:

    $ oc describe pod <pod_name>
  2. Review the pod logs:

    $ oc logs <pod_name>
  3. Examine the output for attestation-related errors, such as:

    • NVIDIA Remote Attestation Service (NRAS) connection failures
    • Policy evaluation errors
    • GPU device allocation issues

If Red Hat build of Trustee cannot connect to NVIDIA Remote Attestation Service (NRAS), verify network connectivity and policies.

Procedure

  1. 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.com

    The command should return HTTP headers indicating successful connectivity.

  2. Verify that network policies allow outbound HTTPS connections to NVIDIA cloud services.
  3. If the connection fails, review your cluster’s egress firewall rules and ensure that traffic to nras.attestation.nvidia.com is permitted.

5.5. Troubleshooting policy evaluation failures

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

  1. Review the attestation policy OPA rules to ensure they are correctly configured for NVIDIA GPU attestation.
  2. Verify that the NRAS claim names in your policy match the expected values from the attestation response.
  3. Check Red Hat build of Trustee logs for policy evaluation details:

    $ oc logs -n trustee-operator-system deployment/trustee-deployment | grep -i "policy"
  4. Review the log output for specific policy evaluation errors or mismatched claim values.

If the GPU is not accessible within the container, verify that the NVIDIA GPU Operator is installed and GPU passthrough is configured correctly.

Procedure

  1. Verify that the NVIDIA GPU Operator is installed on your cluster:

    $ oc get pods -n nvidia-gpu-operator
  2. Check the worker node for GPU visibility:

    $ oc debug node/<worker_node_name> -- chroot /host nvidia-smi

    The command should list available GPU devices.

  3. Verify that GPU passthrough is configured correctly on the worker node.
  4. Ensure that the pod requesting the GPU has the correct resource limits specified in its configuration.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top