Oadm: Difference between revisions
Jump to navigation
Jump to search
(8 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
=Internal= | =Internal= | ||
* [[OpenShift Command Line Tools#Overview|OpenShift Command Line Tools]] | |||
* [[OpenShift Operations#Subjects|OpenShift Operations]] | * [[OpenShift Operations#Subjects|OpenShift Operations]] | ||
* [[oc]] | * [[oc]] | ||
Line 6: | Line 7: | ||
=Overview= | =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#Overview|oc]]. | 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#Overview|oc]]. For more details on CLI tool configuration and context see: {{Internal|OpenShift Command Line Tools#Overview|OpenShift Command Line Tools}} | ||
= | =Namespace Selection= | ||
{{Internal|OpenShift_Command_Line_Tools#Namespace_Selection|CLI Tools Namespace Selection}} | |||
=General Options= | =General Options= | ||
Line 29: | Line 30: | ||
* <span id="policy"></span>[[policy]] | * <span id="policy"></span>[[policy]] | ||
* <span id="router"></span>[[oadm router|router]] | * <span id="router"></span>[[oadm router|router]] | ||
* <span id="drain"></span>[[oadm drain|drain]] | |||
* <span id="registry"></span>[[oadm registry|registry]] | |||
=Questions= | =Questions= |
Latest revision as of 20:48, 6 December 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. For more details on CLI tool configuration and context see:
Namespace Selection
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?