KUBERNETES(1)(kubernetes)

✨ NAME ✨

kubectl uncordon β€” mark a node as schedulable again, bestie πŸ’–

(it lives in the kubernetes manual, section 1, and it was written by Eric Paris back in Jan 2015 β€” we'll get to that later, don't worry 🫢)


🌸 SYNOPSIS 🌸

kubectl uncordon [OPTIONS]

πŸ¦‹ DESCRIPTION πŸ¦‹

Mark node as schedulable. That's it. That's the whole vibe. ✨

Like, if you ever cordoned a node (aka told the scheduler "girl, don't put anything new here πŸ’…"), this is the glow-up that undoes it. Node's back on the market. Main character energy restored. πŸ‘‘


πŸ’… OPTIONS πŸ’…

  • --dry-run="none" β€” okay so this one has three modes and you gotta pick one: "none", "server", or "client". If you go with the client strategy, it literally just prints the object it would have sent β€” nothing actually gets sent, no cap. If you go server strategy, it submits the request server-side but doesn't persist the resource. Very "look but don't touch" of it. πŸ™ˆ
  • -l, --selector="" β€” this is your label query filter πŸŽ€ it supports '=', '==', '!=', 'in', 'notin'. Example vibes: -l key1=value1,key2=value2,key3 in (value3). Whatever objects match have to satisfy all of the label constraints you listed β€” every single one, periodt.

πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

(these are the ones kubectl hands down to every child command, like family heirlooms but for flags 🌈)

  • --as="" β€” username to impersonate for the operation. Could be a regular user, could be a service account in a namespace. Either way, you're wearing their face. 🧚
  • --as-group=[] β€” group to impersonate for the operation. This flag can be repeated to specify multiple groups, so go off.
  • --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. Iconic, honestly.
  • --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, you opt out of response compression for all requests to the server. All of them. Every single one. πŸ’€
  • --insecure-skip-tls-verify=false β€” if true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure. Yes bestie, that's exactly as risky as it sounds. 🚨
  • --kubeconfig="" β€” path to the kubeconfig file to use for CLI requests.
  • --kuberc="" β€” path to the kuberc file to use for preferences. You can disable this by exporting KUBECTL_KUBERC=false feature gate, or by turning off the feature with KUBERC=off. Two whole ways to say no. πŸ™…
  • --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). Pick your fighter. ⭐
  • --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" β€” how long 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 β€” live dangerously, I guess. 😭
  • -s, --server="" β€” the address and port of the Kubernetes API server.
  • --tls-server-name="" β€” server name to use for server certificate validation. If it's 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. Harsh but fair. πŸ”₯

πŸ“ EXAMPLE πŸ“

# Mark node "foo" as schedulable
kubectl uncordon foo

πŸ’œ SEE ALSO πŸ’œ


🌸 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! πŸŽ€


okay that's the whole page bestie, go forth and uncordon responsibly 🫢✨

Manuals Β· User Β· KUBERNETES(1)(kubernetes) Β· and yeah, it's dated Jan 2015 β€” vintage, iconic, still slaying πŸ’…πŸ‘‘

πŸ“¦ where this page comes from