OpenShift Command Line Tools: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= * OpenShift_Concepts#Command_Line_Tools =Overview= User may interact with OpenShift by sending REST API invocations into an OpenShift mast...") |
|||
| Line 6: | Line 6: | ||
User may interact with OpenShift by sending REST API invocations into an OpenShift master. Any user may send project-related queries and administrative commands with [[oc]]. Special administrative commands related to core OpenShift services may be sent with [[oadm]] | User may interact with OpenShift by sending REST API invocations into an OpenShift master. Any user may send project-related queries and administrative commands with [[oc]]. Special administrative commands related to core OpenShift services may be sent with [[oadm]] | ||
=CLI Tool Context= | |||
A command line tool ([[oc]] or [[oadm]]) maintains state on the client host, and an essential part of the state is the ''context''. A context consists in a project (namespace) name, an OpenShift cluster address, and the name of the OpenShift user under | |||
Context examples: | |||
default/lb-local:443/system:admin | |||
or | |||
playground/master-openshift-novaordis-io:443/ovidiu | |||
Revision as of 21:11, 18 October 2017
Internal
Overview
User may interact with OpenShift by sending REST API invocations into an OpenShift master. Any user may send project-related queries and administrative commands with oc. Special administrative commands related to core OpenShift services may be sent with oadm
CLI Tool Context
A command line tool (oc or oadm) maintains state on the client host, and an essential part of the state is the context. A context consists in a project (namespace) name, an OpenShift cluster address, and the name of the OpenShift user under
Context examples:
default/lb-local:443/system:admin
or
playground/master-openshift-novaordis-io:443/ovidiu