OC-SET-DATA(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

🎀 OC SET DATA 🎀

okay bestie, welcome to the oc set data page — this is the oc set family, June 2016 edition, and honestly? it's giving "tiny command, huge glow-up." let's get into it 💅

✨ NAME ✨

oc set data — Update the data within a config map or secret 🗂️

🦋 SYNOPSIS 🦋

oc set data [OPTIONS]

🌸 DESCRIPTION 🌸

So what does this actually do? It adds, updates, or removes data keys from secrets and config maps. Lowkey essential.

Secrets and config maps are how users store keys and values that can be passed into pods or loaded by other Kubernetes resources — think of them as the little velvet pouches where your cluster keeps its stuff 🫶. This command lets you set or remove keys from those objects, straight from arguments or from files.

Use the --from-file flag when you want to load the contents of a file or directory. Or pass command line arguments that contain either a KEY=VALUE pair (to set a value) or KEY- (to remove that key). That trailing dash is the whole "delete this" energy, no cap ✨.

You may also use this command as part of a chain to modify an object before submitting to the server with the --local and --dry-run flags. This allows you to update local resources to contain additional keys — like a vibe check before the actual commit 😌.

💖 OPTIONS 💖

  • --all=false — If true, select all resources in the namespace of the specified resource types. (default: false, so like, no, not all of them 🙈)
  • --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. Default is true, very forgiving of you 💜
  • --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, basically 🛍️
  • --field-manager="kubectl-set" — Name of the manager used to track field ownership. Default is kubectl-set.
  • -f, --filename=[] — Filename, directory, or URL to files to use to edit the resource.
  • --from-file=[] — Specify a file using its file path, in which case the file basename will be used as the key, or optionally with a key and file path, in which case the given key will be used. Specifying a directory will iterate each named file in the directory whose basename is a valid secret key. So many files, so little time 🍓
  • --from-literal=[] — Specify a key and literal value to set (i.e. mykey=somevalue).
  • -k, --kustomize="" — Process the kustomization directory. This flag can't be used together with -f or -R. Pick a lane, bestie 😤
  • --local=false — If true, set image will NOT contact api-server but run locally. Notice it says "set image" — that's the original wording, not me being chaotic, I promise 😭
  • -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. Go deep, icon 👑
  • -l, --selector="" — Selector (label query) to filter on.
  • --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 are the ones you didn't ask for but you're getting anyway, and honestly they ate 💀

  • --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. yes that's the literal default path, yes it's a little unhinged, moving on 🧚
  • --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. ⚠️ genuinely insecure, no cap, be careful
⚠️ heads up bestie: --insecure-skip-tls-verify=false is the safe default — flipping it to true means the server's certificate will not be checked for validity and your HTTPS connections will be insecure. That's not a vibe, that's a real security note.
  • --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. Patient queen energy ⏳
  • -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. Strict queen 🌈

🔥 EXAMPLE 🔥

okay these are the actual examples, copied exactly, slay:

# Set the 'password' key of a secret
oc set data secret/foo password=this_is_secret

# Remove the 'password' key from a secret
oc set data secret/foo password-

# Update the 'haproxy.conf' key of a config map from a file on disk
oc set data configmap/bar --from-file=../haproxy.conf

# Update a secret with the contents of a directory, one key per file
oc set data secret/foo --from-file=secret-dir

see how password=this_is_secret sets it and password- yeets it? that's the whole trick 💅✨

🌈 SEE ALSO 🌈

🦋 HISTORY 🦋

June 2016, Ported from the Kubernetes man-doc generator. vintage, honestly 📼

and that's the page, bestie 🫶 — this one came out of Openshift, in the Openshift CLI User Manuals, dated June 2016, and yes the page is literally titled OC SET(1) up top. go set some data, you're gonna do great 💖

📦 where this page comes from