KUBERNETES(1)(kubernetes)

👑 KUBERNETES(1)(kubernetes) — bestie edition

okay so this is the manual page for kubectl set resources, and honestly? it's giving "I will personally manage your pod's CPU feelings" energy. it lives in the kubernetes manual, and the original was written by Eric Paris back in Jan 2015. hi Eric, legend behavior. 💖

---

✨ NAME ✨

kubectl set resources — update resource requests/limits on objects with pod templates

no cap, that's the whole vibe: you're going in and telling your objects how much CPU and memory they get to have. periodt.

---

🌸 SYNOPSIS 🌸

kubectl set resources [OPTIONS]

---

🦋 DESCRIPTION 🦋

so bestie, here's the tea ☕ — you're specifying compute resource requirements (CPU, memory) for any resource that defines a pod template. like, any of them. go off.

and if a pod actually gets successfully scheduled? it is guaranteed the amount of resource it requested. but it may also burst up to its specified limits. so it's like, "you have a baseline, but you can pop off if you need to." main character energy fr fr.

for each compute resource, if a limit is specified and a request is omitted, the request will default to the limit. so the limit is doing double duty, cute.

possible resources include (case insensitive): use kubectl api-resources for a complete list of supported resources.. yes there's a double period at the end, I'm not fixing it, that's just how she wrote it 💅

---

💅 OPTIONS 💅

• --all=false — select all resources, in the namespace of the specified resource types. every single one. all of them. obsessed.
• --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.
• -c, --containers="*" — the names of containers in the selected pod templates to change, all containers are selected by default — may use wildcards. wildcards!! she's flexible 🎀
• --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. window shopping but for yaml.
• --field-manager="kubectl-set" — name of the manager used to track field ownership. somebody has to keep track of who touched what 👀
• -f, --filename=[] — filename, directory, or URL to files identifying the resource to get from a server.
• -k, --kustomize="" — process the kustomization directory. this flag can't be used together with -f or -R. they are NOT friends, do not invite them to the same party.
• --limits="" — the resource requirement requests for this container. for example, 'cpu=100m,memory=256Mi'. note that server side components may assign requests depending on the server configuration, such as limit ranges.
• --local=false — if true, set resources will NOT contact api-server but run locally. it's just you and your laptop, no server, no drama.
• -o, --output="" — output format. one of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
• --record=false — record current kubectl command in the resource annotation. if set to false, do not record the command. if set to true, record the command. if not set, default to updating the existing annotation value only if one already exists.
• -R, --recursive=false — process the directory used in -f, --filename recursively. useful when you want to manage related manifests organized within the same directory. going deep, going thorough 🔥
• --requests="" — the resource requirement requests for this container. for example, 'cpu=100m,memory=256Mi'. note that server side components may assign requests depending on the server configuration, such as limit ranges.
• -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.
• --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 🌈

these ones came with the family, they're inherited, we love a legacy 💜

• --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 — bestie, do NOT casually turn this on, it's giving red flag 🚩
• --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. zero = patient icon ✨
• -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
• --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

---

🍓 EXAMPLE 🍓

here's where it gets fun, run these, they ate 💖

# Set a deployments nginx container cpu limits to "200m" and memory to "512Mi"
kubectl set resources deployment nginx -c=nginx --limits=cpu=200m,memory=512Mi

# Set the resource request and limits for all containers in nginx
kubectl set resources deployment nginx --limits=cpu=200m,memory=512Mi --requests=cpu=100m,memory=256Mi

# Remove the resource requests for resources on containers in nginx
kubectl set resources deployment nginx --limits=cpu=0,memory=0 --requests=cpu=0,memory=0

# Print the result (in yaml format) of updating nginx container limits from a local, without hitting the server
kubectl set resources -f path/to/file.yaml --limits=cpu=200m,memory=512Mi --local -o yaml

---

🫶 SEE ALSO 🫶

• kubectl-set(1),

go read that one next, iykyk 💜

---

🧚 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! shoutout to the auto-generation pipeline, doing the lord's work 🙈

---

okay that's the whole page bestie, you're officially certified in kubectl set resources 💅✨

this was the User manual, page KUBERNETES(1)(kubernetes), and yes the footer really is just Manuals / User / KUBERNETES(1)(kubernetes) — iconic, no notes 🎀