Description of problem:

Sandbox containers documentation outlines that nodes can be labelled so sandboxed containers can be scheduled to them. An increasing customer use case is mixed physical/virtual nodes on a cluster, which can be achieved with a provider agnostic UPI install.

Given the support stance of not providing support for nested virt, the documentation should address how the admin of a cluster, installing kata operator can identify and label their BM nodes correctly. We can't assume the person deploying kata has intricate cluster or openshift knowledge to work this out for themselves.

This will help to ensure customers are not unknowingly running kata workloads using nested virt and therefore unsupported.

https://deploy-preview-40069--osdocs.netlify.app/openshift-enterprise/latest/sandboxed_containers/deploying-sandboxed-container-workloads.html#sandboxed-containers-create-kataconfig-resource-web-console_deploying-sandboxed-containers

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info: