Oc describe: Difference between revisions
Jump to navigation
Jump to search
Line 9: | Line 9: | ||
oc describe supports the following generic syntax: | oc describe supports the following generic syntax: | ||
oc describe ''<componentType>''/''<componentName>'' | oc describe ''<[[OpenShift Component Types#Overview|componentType]]>''/''<componentName>'' | ||
oc describe daemonset/logging-fluentd | oc describe daemonset/logging-fluentd |
Revision as of 18:04, 12 October 2017
Internal
Overview
Generic Syntax
oc describe supports the following generic syntax:
oc describe <componentType>/<componentName>
oc describe daemonset/logging-fluentd oc describe node/node1 oc describe pod/logging-fluentd-3kz30
The same pattern applies for oc edit.
For a complete list of OpenShift component types, see
Subcommands
group
Describe groups.
oc describe group
quota
oc describe quota core-object-counts -n demo project
pod
Find the pod name with
oc get pod -n <some-namespace>
Then get more information:
oc describe pod -n <some-namespace> <pod-name>
Example:
oc describe pod -n logging logging-kibana-1-d4bw2
Alternative:
oc describe -n logging po/logging-kibana-1-d4bw2
Output Example:
node
oc describe node <node-name>
can be used to get the labels applied to the node.