OC-POLICY-REMOVE-USER(1)
β¨ oc policy remove-user β¨
okay bestie, welcome to the oc policy manual π
this one is literally all about kicking a user out of a project, and i'm gonna walk you through every single flag so you don't have to guess. no cap, we're covering everything.
πΈ SYNOPSIS πΈ
oc policy remove-user [OPTIONS]
π DESCRIPTION π
Remove user from the project π that's the whole vibe. short, iconic, to the point. you're removing a user from the project, periodt.
π OPTIONS π
--allow-missing-template-keys=trueβ if true, ignore any errors in templates when a field or map key is missing in the template. only applies togolangandjsonpathoutput formats, so don't @ me if it doesn't do anything elsewhere.--dry-run="none"β must be"none","server", or"client". if client strategy, only print the object that would be sent, without sending it. if server strategy, submit server-side request without persisting the resource. it's giving "look but don't touch" energy π₯-o, --output=""β output format. one of:(json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). pick your fighter π«Ά--show-managed-fields=falseβ if true, keep themanagedFieldswhen printing objects in JSON or YAML format. lowkey a niche one but we respect it.--template=""β template string or path to template file to use when-o=go-template,-o=go-template-file. the template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview]. iconic, honestly.
π OPTIONS INHERITED FROM PARENT COMMANDS π
these are the flags you get from the parent command, and yes they all matter π
--as=""β username to impersonate for the operation. user could be a regular user or a service account in a namespace. main character energy, but make it someone else π--as-group=[]β group to impersonate for the operation, this flag can be repeated to specify multiple groups. stack 'em up, bestie.--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. again with the repeating, we love a flexible flag β¨--cache-dir="/homeless-shelter/.kube/cache"β default cache directory. that path is exactly what it says, don't come for me.--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 β οΈ like, for real, be careful with this one.--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. yes, that's the whole instruction, don't overthink it π¦--match-server-version=falseβ require server version to match client version. strict queen behavior.-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). pick a profile bestie π--profile-output="profile.pprof"β name of the file to write the profile to. default filename is literallyprofile.pprof, keep it or change it, your call.--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. zero = infinite patience, no cap π-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 π dramatic but valid.
π«Ά SEE ALSO π«Ά
π¦ HISTORY π¦
June 2016, Ported from the Kubernetes man-doc generator
and that's the whole page, bestie! π this was oc policy remove-user from the Openshift CLI User Manuals, brought to you by Openshift and dated June 2016. slay, you're now fully caught up β¨π
π¦ 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