OC-ADM-POLICY-ADD-SCC-TO-GROUP(1)

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

okay bestie, welcome to OC ADM POLICY(1) energy, specifically the oc adm policy add-scc-to-group(1) page β€” yes, we're adding a security context constraint to groups and we're gonna understand every flag, no cap. πŸ’…βœ¨

🌸 NAME 🌸

oc adm policy add-scc-to-group β€” add a security context constraint to groups. that's the whole assignment, and it ate. 🫢

✨ SYNOPSIS ✨

oc adm policy add-scc-to-group [OPTIONS]

πŸ’– DESCRIPTION πŸ’–

Add a security context constraint to groups. iconic behavior, honestly. πŸŽ€

πŸŽ€ OPTIONS πŸŽ€

  • --allow-missing-template-keys=true β€” when this is true, ignore any errors in templates when a field or map key is missing in the template. only applies to golang and jsonpath output formats, bestie.
  • --dry-run="none" β€” must be "none", "server", or "client". if it's the client strategy, only print the object that would be sent, without sending it. if it's the server strategy, submit a server-side request without persisting the resource. very "look but don't touch" of it. πŸ‘€
  • -o, --output="" β€” output format. one of: json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file.
  • --show-managed-fields=false β€” if true, keep the managedFields when printing objects in JSON or YAML format.
  • --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⟩].

πŸ¦‹ 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. like, actually insecure, so be dramatic about it if you need to. πŸ’€
  • --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 exporting KUBECTL_KUBERC=false feature gate or turning off the feature KUBERC=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 🌈

# Add the 'restricted' security context constraint to group1 and group2
oc adm policy add-scc-to-group restricted group1 group2

πŸ”₯ SEE ALSO πŸ”₯

πŸ’œ HISTORY πŸ’œ

  • June 2016, Ported from the Kubernetes man-doc generator

signed off with source/version Openshift CLI User Manuals and date June 2016 β€” periodt, go add that SCC to those groups bestie πŸ«Άβœ¨πŸ’…

πŸ“¦ where this page comes from