Oc login: Difference between revisions
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
Establishes an authenticated command-line session with the server and saves configuration under <.kube/config.If there is no state saved under .kube/config, it queries the user for OpenShift server, username and password. | Establishes an authenticated command-line session with the server and saves configuration under <tt>.kube/config</tt>.If there is no state saved under .kube/config, it queries the user for OpenShift server, username and password. | ||
The user must exists on server, and its identity must be correctly resolved by the OpenShift identity provider. | The user must exists on server, and its identity must be correctly resolved by the OpenShift identity provider. | ||
Revision as of 19:17, 5 July 2017
Internal
Overview
Establishes an authenticated command-line session with the server and saves configuration under .kube/config.If there is no state saved under .kube/config, it queries the user for OpenShift server, username and password.
The user must exists on server, and its identity must be correctly resolved by the OpenShift identity provider.
Example:
oc login -u system:admin
If -u is not specified, oc login will query for user.
More about authentication:
Options
-u --username
Sets the user name.
-p --password
Sets the user name.
-n
Sets the project (namespace) to log into.
-s --server
--server="https://my-openshift-master:8443"
--certificate-authority
Specifies the path to the certificate authority file.
--insecure-skip-tls-verify
Allows interaction with HTTPS server while bypassing server certificate checks.