Oadm: Difference between revisions
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
=Configuration= | =Configuration= | ||
<tt>oadm</tt> reads its configuration from [[.kube/config|~<''unix-user''>/.kube/config]] and based on this information, establishes the client-side and server-side context of the REST client that is used to send invocation into the OpenShift master. | <tt>oadm</tt> reads its configuration from [[.kube/config|~<''unix-user''>/.kube/config]] and based on this information, establishes the client-side and server-side context of the REST client that is used to send invocation into the OpenShift master. Some of the contextual information is then cached in a cluster-specifc directory: ~<''unix-user''>/.kube/<''cluster-name''> | ||
=General Options= | =General Options= | ||
Revision as of 21:00, 18 October 2017
Internal
Overview
The cluster administrator's CLI interface. There is no oadm release for common clients, which probably means it is intended to be only used on the server. The general user OpenShift CLI interface is oc.
Configuration
oadm reads its configuration from ~<unix-user>/.kube/config and based on this information, establishes the client-side and server-side context of the REST client that is used to send invocation into the OpenShift master. Some of the contextual information is then cached in a cluster-specifc directory: ~<unix-user>/.kube/<cluster-name>
General Options
--loglevel
oadm --loglevel=n command ...
where n is 0-10.
Commands
Questions
- Can oadm be installed on an access host, other than the master(s), so it allows cluster administration without being physically present on the master?