OC(1)
π
oc login β Log in to a server π
okay so bestie, welcome to OC(1) β the manual page for oc login, aka your lil glow-up portal into a server. β¨ We're gonna get you logged in and it's gonna slay.
πΈ NAME πΈ
oc login β Log in to a server. π
β¨ SYNOPSIS β¨
oc login [OPTIONS]
π¦ DESCRIPTION π¦
Log in to your server and save login for subsequent use. π«
First-time users of the client should run this command to connect to a server, establish an authenticated session, and save connection to the configuration file. The default configuration will be saved to your home directory under .kube/config. π‘
The information required to login β like username and password, a session token, or the server details β can be provided through flags. If not provided, the command will prompt for user input as needed. It is also possible to login through a web browser by providing the respective flag. π
π OPTIONS π
--auto-open-browser=falseβ Experimental: Automatically open browser for login. When used with--web, defaults totrue. When used with--exec-pluginfor external OIDC, defaults tofalse.-c,--callback-port=0β Port for the callback server when using--web. Defaults to a random open port.--client-id=""β Experimental: Client ID for external OIDC issuer. Only supports Auth Code + PKCE. Required.--client-secret=""β Experimental: Client secret for external OIDC issuer. Optional.--exec-plugin=""β Experimental: Specify credentials exec plugin type to be used to authenticate external OIDC issuer. Currently only'oc-oidc'is supported.--extra-scopes=[]β Experimental: Extra scopes for external OIDC issuer. Optional.--issuer-url=""β Experimental: Issuer url for external issuer. Required.--oidc-certificate-authority=""β Experimental: The path to a certificate authority bundle to use when communicating with external OIDC issuer.-p,--password=""β Password for server.-u,--username=""β Username for server.-w,--web=falseβ Login with web browser. Starts a local HTTP callback server to perform the OAuth2 Authorization Code Grant flow. Use with caution on multi-user systems, as the server's port will be open to all users. β οΈ
π«Ά OPTIONS INHERITED FROM PARENT COMMANDS π«Ά
--as=""β Username to impersonate for the operation. User could be a regular user or a service account in a namespace.--as-group=[]β Group to impersonate for the operation, this flag can be repeated to specify multiple groups.--as-uid=""β UID to impersonate for the operation.--as-user-extra=[]β User extras to impersonate for the operation, this flag can be repeated to specify multiple values for the same key.--cache-dir="/homeless-shelter/.kube/cache"β Default cache directory.--certificate-authority=""β Path to a cert file for the certificate authority.--client-certificate=""β Path to a client certificate file for TLS.--client-key=""β Path to a client key file for TLS.--cluster=""β The name of the kubeconfig cluster to use.--context=""β The name of the kubeconfig context to use.--disable-compression=falseβ If true, opt-out of response compression for all requests to the server.--insecure-skip-tls-verify=falseβ If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure. π¨--kubeconfig=""β Path to the kubeconfig file to use for CLI requests.--kuberc=""β Path to the kuberc file to use for preferences. This can be disabled by exportingKUBECTL_KUBERC=falsefeature gate or turning off the featureKUBERC=off.--match-server-version=falseβ Require server version to match client version.-n,--namespace=""β If present, the namespace scope for this CLI request.--profile="none"β Name of profile to capture. One of(none|cpu|heap|goroutine|threadcreate|block|mutex).--profile-output="profile.pprof"β Name of the file to write the profile to.--request-timeout="0"β The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g.1s,2m,3h). A value of zero means don't timeout requests.-s,--server=""β The address and port of the Kubernetes API server.--tls-server-name=""β Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used.--token=""β Bearer token for authentication to the API server.--user=""β The name of the kubeconfig user to use.--warnings-as-errors=falseβ Treat warnings received from the server as errors and exit with a non-zero exit code.
π EXAMPLE π
# Log in interactively
oc login --username=myuser
# Log in to the given server with the given certificate authority file
oc login localhost:8443 --certificate-authority=/path/to/cert.crt
# Log in to the given server with the given credentials (will not prompt interactively)
oc login localhost:8443 --username=myuser --password=mypass
# Log in to the given server through a browser
oc login localhost:8443 --web --callback-port 8280
# Log in to the given server through a browser without opening it automatically (print URL only)
oc login localhost:8443 --web --auto-open-browser=false --callback-port 8280
# Log in to the external OIDC issuer through Auth Code + PKCE by starting a local server listening on port 8080
oc login localhost:8443 --exec-plugin=oc-oidc --client-id=client-id --extra-scopes=email,profile --callback-port=8080
π₯ SEE ALSO π₯
Go peek at oc(1), β yes bestie, the comma is canon. π
π HISTORY π
June 2016, Ported from the Kubernetes man-doc generator β iconic origin story. π
okay that's the whole page, bestie. π Source/version: Openshift β Openshift CLI User Manuals; date: June 2016; manual: OC(1). byeee π«Άβ¨
π¦ where this page comes from
- nixpkgs unstable: openshift 4.22.0-202605222050
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms