KUBERNETES(1)(kubernetes)

💅 KUBERNETES(1)(kubernetes) 💅

okay bestie, welcome to the KUBERNETES(1)(kubernetes) manual — this one's by Eric Paris, Jan 2015, and it's all about one very specific lil' glow-up: kubectl set subject. it does exactly one thing and it does it slay. let's get into it 🫶

---

✨ NAME ✨

kubectl set subject — Update the user, group, or service account in a role binding or cluster role binding

like. it changes who is bound. that's the whole vibe. 💫

---

🦋 SYNOPSIS 🦋

kubectl set subject [OPTIONS]

---

🌸 DESCRIPTION 🌸

Update the user, group, or service account in a role binding or cluster role binding.

that's it, that's the girl. you point her at a binding and you're like "hey, these people/accounts are in this now" and she's like "say less" and does it. 👑

---

💖 OPTIONS 💖

• --all=false — select all the resources, but only within the namespace of the resource types you named. no cap, it's scoped.
• --allow-missing-template-keys=true — when it's true, template errors about a missing field or map key just... get ignored, bestie. 🙈 only applies to the golang and jsonpath output formats, so don't get any ideas elsewhere.
• --dry-run="none" — has to be "none", "server", or "client". with the client strategy she only prints the object she would have sent — never sends it. with server she submits a server-side request but doesn't persist the resource. a lil dress rehearsal, no commitment. 💅
• --field-manager="kubectl-set" — the name of the manager used to track field ownership. that's the label on who touched what.
• -f, --filename=[] — filename, directory, or URL to files the resource to update the subjects. give her a path, she'll find it.
• --group=[] — groups to bind to the role.
• -k, --kustomize="" — process the kustomization directory. ⚠️ this flag can't be used together with -f or -R — pick a lane, babe.
• --local=false — if true, set subject will NOT contact api-server but run locally. offline mode, main character energy. 🧚
• -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. super 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 — she's picky and we love that.
• --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. receipts stay visible. 🧾
• --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 🌈

these are the ones she got from her mom kubectl. still iconic.

• --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="/home/username/.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, genuinely insecure, not a cute lil insecure. be careful.
• --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.
• --password="" — password for basic authentication to the API server.
• --profile="none" — name of profile to capture. one of (none|cpu|heap|goroutine|threadcreate|block|mutex|trace).
• --profile-output="profile.pprof" — name of the file to write the profile to.
• --proxy-url="" — proxy URL to use for requests to the API server.
• --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.
• --username="" — username for basic authentication to the API server.
• --version=false — --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version.
• --warnings-as-errors=false — treat warnings received from the server as errors and exit with a non-zero exit code. 😤 zero tolerance policy, honestly.

---

🔥 EXAMPLE 🔥

okay here's the part where she eats. 💅

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

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

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

that last one is the pipe dream (literally, it's a pipe 😭) — --local + -f - means she never even phones the server. obsessed.

---

👀 SEE ALSO 👀

• kubectl-set(1),

go read her sister page, she's also great.

---

📜 HISTORY 📜

January 2015, originally compiled by Eric Paris (eparis at redhat dot com) based on the kubernetes source material, but hopefully they have been automatically generated since!

---

and that's the whole page, bestie 🎀 this was the Manuals / User one, dated KUBERNETES(1)(kubernetes) — so go forth, bind those subjects, and remember: --insecure-skip-tls-verify is not the vibe. mwah. 💖✨🦋