Oc edit: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 11: | Line 11: | ||
oc edit supports the following generic syntax: | oc edit supports the following generic syntax: | ||
oc edit ''<[[ | oc edit ''<[[Oc_types#OpenShift_Component_Types|componentType]]>''/''<componentName>'' | ||
oc edit daemonset/logging-fluentd | oc edit daemonset/logging-fluentd | ||
| Line 20: | Line 20: | ||
The same pattern applies for [[oc describe#Generic_Syntax|oc describe]]. | The same pattern applies for [[oc describe#Generic_Syntax|oc describe]]. | ||
For a complete list of OpenShift component types, see {{Internal| | For a complete list of OpenShift component types, see {{Internal|Oc_types#OpenShift_Component_Types|OpenShift Component Types}} | ||
=Sub-Commands= | =Sub-Commands= | ||
oc edit project ''<project-name>'' | oc edit project ''<project-name>'' | ||
Revision as of 21:11, 20 November 2017
Internal
Overview
In-line metadata editing with vi. Exposes the metadata in YAML format for editing.
Generic Syntax
oc edit supports the following generic syntax:
oc edit <componentType>/<componentName>
oc edit daemonset/logging-fluentd oc edit node/node1 oc edit pod/logging-fluentd-3kz30 oc edit oauthclient/kibana-proxy
The same pattern applies for oc describe.
For a complete list of OpenShift component types, see
Sub-Commands
oc edit project <project-name>