Bug 2050645

Summary:	[RFE] Document how a user can identify and label BM nodes for scheduling sandbox containers
Product:	OpenShift Container Platform	Reporter:	Timothy Rees <trees>
Component:	sandboxed-containers	Assignee:	Ariel Adam <aadam>
Status:	CLOSED DEFERRED	QA Contact:	Cameron Meadors <cmeadors>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	aos-bugs, mkalinin
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-09 01:12:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Timothy Rees 2022-02-04 12:07:00 UTC

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:

Comment 1 Shiftzilla 2023-03-09 01:12:23 UTC

OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira.

https://issues.redhat.com/browse/OCPBUGS-9106