OC-POLICY-REMOVE-ROLE-FROM-GROUP(1)
π
OC POLICY(1) β oc policy remove-role-from-group
okay so first things first, bestie: this is a page from the Openshift CLI User Manuals (the oc fam π), dated June 2016 β yes she's an elder icon but she still slays. Let's get into it β¨
β¨ NAME β¨
oc policy remove-role-from-group β literally just removes a role from groups for the project. that's the whole gig. π
π¦ SYNOPSIS π¦
oc policy remove-role-from-group [OPTIONS]
no positional args, no drama, just flags. periodt. π
πΈ DESCRIPTION πΈ
Remove a role from groups for the project. that's it, that's the vibe check. you point it at groups, it takes the role away. iconic, lowkey devastating for whoever had that role, but that's the job. π
π OPTIONS π
--allow-missing-template-keys=trueβ iftrue, ignore any errors in templates when a field or map key is missing in the template. ngl this only applies togolangandjsonpathoutput formats, so don't come for her if it does nothing elsewhere π«Ά--dry-run="none"β must be"none","server", or"client". if it's the client strategy, it only prints the object that would be sent, without actually sending it (peek, don't touch β¨). if it's the server strategy, it submits a server-side request without persisting the resource β a little rehearsal, no commitment π-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 aesthetic π--role-namespace=""β namespace where the role is located: empty means a role defined in cluster policy. iykyk, cluster-wide vs namespaced is a whole personality trait π--rolebinding-name=""β name of the rolebinding to modify. if left empty it will operate on all rolebindings β so bestie, please know what you're doing before you leave it blank ππ₯--show-managed-fields=falseβ iftrue, keep themanagedFieldswhen printing objects in JSON or YAML format. for the forensic girlies π--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β© ]. go off, hand-craft your output π
π OPTIONS INHERITED FROM PARENT COMMANDS π
these come from the parent command, so you get them for free β heirloom pieces π§
--as=""β username to impersonate for the operation. user could be a regular user or a service account in a namespace. main character energy, but borrowed π--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 (yes that path is literally real, we don't make the rules π)--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β iftrue, opt-out of response compression for all requests to the server--insecure-skip-tls-verify=falseβ iftrue, the server's certificate will not be checked for validity. β οΈ > this will make your HTTPS connections insecure β like, actually insecure, not cute-insecure. don't do this in prod bestie π--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 π₯
π SEE ALSO π
oc-policy(1)β her mother, go say hi π«Ά
π HISTORY π
June 2016, Ported from the Kubernetes man-doc generator β a vintage moment, honestly. respect the lineage π
and that's the whole page, bestie!! no cap, you're now legally certified in oc policy remove-role-from-group. go be great π
β¨
β signed with love by Openshift, from the Openshift CLI User Manuals, dated June 2016 π¦πΈπ
π¦ 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