OC-SET-SUBJECT(1)

💅 oc set subject — OC SET(1) ✨

okay bestie, this is the oc set subject page from Openshift CLI User Manuals, manual page OC SET(1), dated June 2016 — and it’s giving “update the people in your role bindings” energy. hiiii 🫶

🎀 NAME 🎀

oc set subject — update the user, group, or service account in a role binding or cluster role binding. slay.

✨ SYNOPSIS ✨

oc set subject [OPTIONS]

🦋 DESCRIPTION 🦋

Update user, group or service account in a role binding or cluster role binding. That’s the whole assignment: you’re updating the subjects on a role binding or cluster role binding. no cap 💖

🌸 OPTIONS 🌸

• --all=false — Select all resources, in the namespace of the specified resource types
• --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 to golang and jsonpath output formats.
• --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.
• --field-manager="kubectl-set" — Name of the manager used to track field ownership.
• -f, --filename=[] — Filename, directory, or URL to files the resource to update the subjects
• --group=[] — Groups to bind to the role
• -k, --kustomize="" — Process the kustomization directory. This flag can’t be used together with -f or -R.
• --local=false — If true, set subject will NOT contact api-server but run locally.
• -o, --output="" — Output format. One of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
• -R, --recursive=false — Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory.
• -l, --selector="" — Selector (label query) to filter on, supports '=', '==', '!=', 'in', 'notin'.(e.g. -l key1=value1,key2=value2,key3 in (value3)). Matching objects must satisfy all of the specified label constraints.
• --serviceaccount=[] — Service accounts to bind to the role
• --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⟩].
• --user=[] — Usernames to bind to the role

💜 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

tiny warning, bestie: that --insecure-skip-tls-verify=false vibe is literally about making HTTPS insecure when you flip it. the manpage said it, not me 💀

• --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
• --warnings-as-errors=false — Treat warnings received from the server as errors and exit with a non-zero exit code

🔥 EXAMPLE 🔥

# Update a cluster role binding for serviceaccount1
oc set subject clusterrolebinding admin --serviceaccount=namespace:serviceaccount1

# Update a role binding for user1, user2, and group1
oc set subject rolebinding admin --user=user1 --user=user2 --group=group1

# Print the result (in YAML format) of updating role binding subjects locally, without hitting the server
oc create rolebinding admin --role=admin --user=admin -o yaml --dry-run | oc set subject --local -f - --user=foo -o yaml

🌈 SEE ALSO 🌈

oc-set(1),

👑 HISTORY 👑

June 2016, Ported from the Kubernetes man-doc generator

---

🫶 source/version: Openshift / Openshift CLI User Manuals; date: June 2016. bye bestie, go update those subjects 💖