OC-POLICY-REMOVE-GROUP(1)

πŸ“¦
version 4.22.0 Β· 2 versions
, in nixpkgs unstable

πŸ’… oc policy remove-group β€” like, the whole manual, but make it make sense

Hey bestie 🫢 so this is from the oc policy family of manual pages (the OpenShift CLI user manuals, June 2016 vintage, iconic behavior) β€” and this particular page is all about one lil' command: oc policy remove-group. No cap, that's the whole vibe.


✨ SYNOPSIS ✨

oc policy remove-group [OPTIONS]

That's it. That's the whole incantation. You run it with whatever flags you want, and it does the thing. πŸŽ€


🌸 DESCRIPTION 🌸

Okay so, genuinely: Remove group from the project.

That's the entire description. Short. Sweet. Main character energy. It removes a group from the project, periodt. πŸ’…


πŸ¦‹ OPTIONS πŸ¦‹

These are the flags that belong to remove-group itself, no hand-me-downs here:

  • --allow-missing-template-keys=true β€” if this is true, all those template errors about a missing field or map key? Ignored, bestie. Not a single tear shed. Only applies to the golang and jsonpath output formats, so don't go thinking it's universal πŸ™ˆ.
  • --dry-run="none" β€” has to be one of "none", "server", or "client". If you pick the client strategy, it only prints the object that would've been sent and never actually sends it. If you pick the server strategy, it submits a server-side request without persisting the resource. Very "look but don't touch" of it ✨.
  • -o, --output="" β€” the 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, the managedFields stay in when printing objects in JSON or YAML format. If false... they don't. Slay.
  • --template="" β€” a template string, or a path to a template file, to use when you're on -o=go-template or -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview] β€” yes, the actual angle brackets, iykyk 🧚.

πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

These bad boys come from the parent command β€” they're not remove-group's own, they're just along for the ride πŸš—:

  • --as="" β€” username to impersonate for the operation. Could be a regular user, could be a service account in a namespace.
  • --as-group=[] β€” group to impersonate for the operation. You can repeat this flag to specify multiple groups πŸ”.
  • --as-uid="" β€” UID to impersonate for the operation.
  • --as-user-extra=[] β€” user extras to impersonate for the operation. Repeatable, so you can specify multiple values for the same key.
  • --cache-dir="/homeless-shelter/.kube/cache" β€” the default cache directory. Yes, that's the literal default path. No, I'm not joking πŸ“.
  • --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, which makes your HTTPS connections insecure. Big warning energy, bestie 😭.
Fr fr: flipping --insecure-skip-tls-verify to true turns off certificate validation and leaves your HTTPS connections insecure. Don't do it casually.
  • --kubeconfig="" β€” path to the kubeconfig file to use for CLI requests.
  • --kuberc="" β€” path to the kuberc file to use for preferences. You can disable this by exporting the KUBECTL_KUBERC=false feature gate, or by turning off the feature with KUBERC=off.
  • --match-server-version=false β€” require the server version to match the client version. Demanding. We respect it πŸ’….
  • -n, --namespace="" β€” if present, the namespace scope for this CLI request.
  • --profile="none" β€” name of the 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" β€” how long 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, apparently 🧘.
  • -s, --server="" β€” the address and port of the Kubernetes API server.
  • --tls-server-name="" β€” server name to use for server certificate validation. If it's not provided, the hostname used to contact the server is used instead.
  • --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. Harsh, but fair πŸ’€.

πŸ”₯ SEE ALSO πŸ”₯

  • oc-policy(1), β€” go read the parent page, bestie, it's giving lore.

πŸ’œ HISTORY πŸ’œ

June 2016, Ported from the Kubernetes man-doc generator. A classic. A vintage. A little piece of history 🌈.


Sign-off time, bestie 🫢✨ β€” this page came to you from Openshift, out of the Openshift CLI User Manuals, dated June 2016. That's the whole footer, and honestly? She ate. πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from