Oc: Difference between revisions
Jump to navigation
Jump to search
(→Output) |
(→Output) |
||
| Line 27: | Line 27: | ||
In case of [[oc get]], the output of the server execution is rendered in JSON/YAML if [[oc get#Output|-o json|yaml is used]]. | In case of [[oc get]], the output of the server execution is rendered in JSON/YAML if [[oc get#Output|-o json|yaml is used]]. | ||
The curl commands used to send the requests are displayed with: | |||
oc --v=10 ... | |||
=Logging and Debugging= | =Logging and Debugging= | ||
Revision as of 03:07, 6 July 2017
External
- https://docs.openshift.com/container-platform/latest/cli_reference/basic_cli_operations.html
- https://docs.openshift.com/container-platform/latest/cli_reference/admin_cli_operations.html
Internal
Overview
oc is the OpenShift remote client that talks with the master API server.
Installation
RHEL: oc can be installed with the atomic-openshift-clients package.
Mac: Download from https://access.redhat.com/downloads/content/290, choose "OpenShift v3.5 MacOSX Client". Then extract the content and place "oc" in PATH.
Output
In general, all oc commands can be configured to send their output in either JSON or YAML format, rather than execute the command.
This is achieved with
oc ... -o json|yaml
In case of oc get, the output of the server execution is rendered in JSON/YAML if -o json|yaml is used.
The curl commands used to send the requests are displayed with:
oc --v=10 ...
Logging and Debugging
oc ... --loglevel=8
This log level shows the API requests made with each command.