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β iftrue, you opt out of response compression for all requests to the server. All of them. Every single one. π--insecure-skip-tls-verify=falseβ iftrue, 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 exportingKUBECTL_KUBERC=falsefeature gate, or by turning off the feature withKUBERC=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=rawprints 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
- arch rolling: kubectl 1.37.2-1 Β· Apache-2.0
- fedora 43: kubernetes1.37-client 1.37.0-3.fc43
- fedora 43: kubernetes1.37-client 1.37.1-1.fc43 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND BSD-3-Clause-HP AND CC-BY-4.0 AND ISC AND MIT AND MPL-2.0
- fedora 44: kubernetes1.37-client 1.37.0-3.fc44
- fedora 44: kubernetes1.37-client 1.37.1-1.fc44 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND BSD-3-Clause-HP AND CC-BY-4.0 AND ISC AND MIT AND MPL-2.0
- nixpkgs unstable: kubectl 1.37.2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms