OpenShift Command Line Tools: Difference between revisions
Jump to navigation
Jump to search
(→State) |
(→State) |
||
| Line 9: | Line 9: | ||
=State= | =State= | ||
Both [[oc]] and [[oadm]] maintain state on the client host, under ~/<''user''>/.kube/<''cluster-identifier''> directories, and configuration in ~/<''user''>/.kube/config. Example: | Both [[oc]] and [[oadm]] maintain state on the client host, under ~/<''user''>/.kube/<''cluster-identifier''> directories, and configuration in [[.kube/config|~/<''user''>/.kube/config]]. Example: | ||
~ovidiu/.kube/master.openshift.novaordis.io_443 | ~ovidiu/.kube/master.openshift.novaordis.io_443 | ||
Revision as of 23:51, 18 October 2017
Internal
Overview
User may interact with OpenShift by sending REST API invocations into an OpenShift master. Project-related queries and administrative commands may be sent with oc. Special administrative commands related to core OpenShift services, may be sent with oadm
State
Both oc and oadm maintain state on the client host, under ~/<user>/.kube/<cluster-identifier> directories, and configuration in ~/<user>/.kube/config. Example:
~ovidiu/.kube/master.openshift.novaordis.io_443
describe the .kube/.../subdirectories.
CLI Tool Context
, 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