Oc login: Difference between revisions
Jump to navigation
Jump to search
| Line 50: | Line 50: | ||
Allows interaction with HTTPS server while bypassing server certificate checks. | Allows interaction with HTTPS server while bypassing server certificate checks. | ||
= | =Operations= | ||
* [[OpenShift Enable system:admin Remote Access|Enable system:admin Remote Access]] | * [[OpenShift Enable system:admin Remote Access|Enable system:admin Remote Access]] | ||
Revision as of 00:58, 20 November 2020
Internal
Overview
'oc login' configures locally a Kubernetes context by updating .kube/config. If it finds no state saved under .kube/config, or no command line options are provided, the command queries the user for OpenShift server, username and password. The command runs in the context of a project. The user must exists on server, and its identity must be correctly resolved by the OpenShift identity provider.
Example:
oc login -u <username>:<password>
oc login <api-server-url> -u <username> -p <password>
If -u is not specified, 'oc login' will query for user.
More about OpenShift authentication:
Related
oc whoami
Options
-u,--username
Sets the user name.
-p,--password
Sets the password.
-n
Sets the project (namespace) to log into.
-s,--server
oc login --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.