1. Proposed title of this feature request
Add the SOSReport collection binaries into RHCOS base to make it easier to collect SOSReports when there are issues with OC nodes communicating with the KubeAPIServer and avoid mirroring steps in disconnected environments.

2. What is the nature and description of the request?
Add the SOSReport collection binaries into RHCOS base to make it easier to collect SOSReports when there are issues with OC nodes communicating with the KubeAPIServer and avoid mirroring steps in disconnected environments.

3. Why does the customer need this? (List the business requirements here)
With the deprecation[1] and eventual [0] removal of the `toolbox` command, the process for collecting SOSReports for the CEE/Support engineers will need to change. Currently the process includes using the toolbox command[2][3], which will configure a Podman-managed Pod/container which provides a number of tools for data collection.

As this process is being deprecated, I request that we incorporate a way of collecting SOSReports into each Node without external dependencies. This will ease the collection of SOSReports when the KubeAPIServer or direct internet access is not easily accessible.

4. List any affected packages or components.
RHCOS / Sos

Resources:
[0] https://issues.redhat.com/browse/PLMCORE-3445
[1] https://docs.openshift.com/container-platform/4.13/release_notes/ocp-4-13-release-notes.html#ocp-4-13-toolbox-deprecation
[2] Generate a SOSReport for OCP 4.x with SSH access
https://access.redhat.com/solutions/3820762
[3] Generate a SOSReport for OCP 4.x without SSH access
https://access.redhat.com/solutions/4387261