diff options
| author | Jake Hunsaker <jhunsake@redhat.com> | 2021-09-30 10:38:18 -0400 |
|---|---|---|
| committer | Jake Hunsaker <jhunsake@redhat.com> | 2021-10-29 12:47:28 -0400 |
| commit | dbc49345384404600f45d68b8d3c6541b2a26480 (patch) | |
| tree | 60802ee5dc53060a0593bd325a6a95349d924acb /man/en | |
| parent | f4af5efdc79aefe1aa685c36d095925bae14dc4a (diff) | |
| download | sos-dbc49345384404600f45d68b8d3c6541b2a26480.tar.gz | |
[transports] Add 'oc' as a transport option for remote nodes
This commit adds a new transport for `sos collect` by leveraging a
locally available `oc` binary that has been properly configured for
access to an OCP cluster.
This transport will allow users to use `sos collect` to collect reports
from an OCP cluster without directly connecting to any of the nodes
involved. We do this by using the `oc` binary to first launch a pod on
target node(s) and then exec our discovery commands and eventual `sos
report` command to that pod. This in turn is dependent on a function API
for the `oc` binary to communicate with. In the event that `oc` is not
__locally__ available or is not properly configured, we will fallback to
the current default of using SSH ControlPersist to directly connect to
the nodes. Otherwise, the OCP cluster will attempt to automatically use
this new transport.
Diffstat (limited to 'man/en')
| -rw-r--r-- | man/en/sos-collect.1 | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/man/en/sos-collect.1 b/man/en/sos-collect.1 index 8ad4fe5e..a1f6c10e 100644 --- a/man/en/sos-collect.1 +++ b/man/en/sos-collect.1 @@ -364,6 +364,7 @@ The types of transports supported are currently as follows: \fBauto\fR Allow the cluster type to determine the transport used \fBcontrol_persist\fR Use OpenSSH's ControlPersist feature. This is the default behavior + \fBoc\fR Use a \fBlocally\fR configured \fBoc\fR binary to deploy collection pods on OCP nodes .TP \fB\-\-tmp\-dir\fR TMP_DIR |