OC-CONFIG-DELETE-USER(1)
π OC CONFIG β delete-user (OC CONFIG(1), bestie edition) π
okay so this is a page from the OpenShift CLI User Manuals (Openshift), and we're deep in oc config territory β the oc config family of commands. June 2016 energy, but the vibes are timeless fr fr.
β¨ NAME β¨
oc config delete-user β Delete the specified user from the kubeconfig
πΈ SYNOPSIS πΈ
oc config delete-user [OPTIONS]
π¦ DESCRIPTION π¦
Delete the specified user from the kubeconfig.
that's it. that's the whole thing. it deletes a user. from the kubeconfig. lowkey iconic for how straightforward it is π
π OPTIONS INHERITED FROM PARENT COMMANDS π
these are the flags you get passed down from the parent command, like hand-me-downs but make it Kubernetes π§
--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=""β use a particular kubeconfig file--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
β οΈ bestie pls note: --insecure-skip-tls-verify genuinely makes your HTTPS connections insecure. it's right there in the text. no cap. π
π₯ EXAMPLE π₯
# Delete the minikube user
oc config delete-user minikube
look at that. clean. effortless. minikube user? gone. poof. π«Ά
π SEE ALSO π
β HISTORY β
June 2016, Ported from the Kubernetes man-doc generator
and that's the whole page!! mwah π sign-off time: this was brought to you by Openshift β Openshift CLI User Manuals, date June 2016, and yes the header up top says OC CONFIG(1) with that same June 2016 date because consistency is the moment. periodt. πβ¨π
π¦ 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