Oc describe: Difference between revisions
Jump to navigation
Jump to search
Line 11: | Line 11: | ||
oc describe ''<componentType>''/''<componentName>'' | oc describe ''<componentType>''/''<componentName>'' | ||
oc describe daemonset/logging-fluentd | |||
oc describe node/node1 | oc describe node/node1 | ||
oc describe | oc describe pod/logging-fluentd-3kz30 | ||
=Subcommands= | =Subcommands= |
Revision as of 23:18, 30 July 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
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.