OC-SET-RESOURCES(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

💅 OC SET(1) — oc set resources

okay bestie, welcome to the oc set resources page from the Openshift CLI User Manuals ✨ pull up a chair, grab a boba, we're doing Kubernetes resource math together 🧋

✨ NAME ✨

oc set resources — update those resource requests/limits on objects that have pod templates 🫶

✨ SYNOPSIS ✨

oc set resources [OPTIONS]

🌸 DESCRIPTION 🌸

So the whole point: you're specifying compute resource requirements (cpu, memory) for literally any resource that defines a pod template. And it's giving "reserved seating" energy — if a pod actually gets scheduled, it is guaranteed the amount of resource it requested, but it may burst up to its specified limits 🔥

And here's a cute little default for you: for each compute resource, if a limit is specified and a request is omitted, the request will just default to the limit. no extra work required, she's self-sufficient 💅

Possible resources include (and yes, case insensitive bestie, we don't gatekeep):

  • "ReplicationController"
  • "Deployment"
  • "DaemonSet"
  • "Job"
  • "ReplicaSet"
  • "DeploymentConfigs"

✨ OPTIONS ✨

  • --all=false — select all the resources, in the namespace of the specified resource types. go big or go home 💖
  • --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 — and yes you may use wildcards, she's flexible like that 🌈
  • --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 👀 lowkey a vibe check before you commit
  • --field-manager="kubectl-set" — name of the manager used to track field ownership 🏷️
  • -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 🚫
  • --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 🏠 main character energy, staying home
  • -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 🦋
  • --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 — no partial credit, she's strict ✨
  • --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 🎀

like, these aren't hers, she inherited them, but they're 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="/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 ⚠️ bestie. please.
  • --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 🌟

okay these are literally the moves, copy them exactly, no freestyling ✨

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

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

# Remove the resource requests for resources on containers in nginx
oc 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 locally, without hitting the server
oc set resources -f path/to/file.yaml --limits=cpu=200m,memory=512Mi --local -o yaml

🦋 SEE ALSO 🦋

💜 HISTORY 💜

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

ngl that's the whole page, bestie — go forth and set those limits 🌸

okay that's a wrap on this one, brought to you by Openshift and the Openshift CLI User Manuals, dated June 2016 — slay, periodt 💅✨

📦 where this page comes from