OC-ADM-CORDON(1)

πŸ“¦
version 4.22.0 Β· 2 versions
, in nixpkgs unstable

πŸ’… oc adm cordon (OpenShift CLI User Manuals, section 1)

okay bestie, welcome to the oc adm cordon page β€” this is from the OpenShift CLI User Manuals, manual section 1, and it's genuinely such a vibe once you get it. let's go πŸŽ€


✨ NAME ✨

oc adm cordon β€” mark a node as unschedulable 🚫

πŸ¦‹ SYNOPSIS πŸ¦‹

oc adm cordon [OPTIONS]

🌸 DESCRIPTION 🌸

Mark node as unschedulable.

that's it. that's the whole thing. no cap, it's giving "short and iconic" πŸ‘‘

πŸ’– OPTIONS πŸ’–

  • --dry-run="none" β€” lowkey a vibe check before you commit πŸ™ˆ. Has to be "none", "server", or "client". With the client strategy, it literally just prints the object that would be sent β€” nothing actually gets sent. With the server strategy, it submits a server-side request but does not persist the resource. so you see the tea without spilling it.
  • -l, --selector="" β€” the label query filter, aka how you pick which cuties you're talking to πŸ’…. Supports '=', '==', '!=', 'in', 'notin' (e.g. -l key1=value1,key2=value2,key3 in (value3)). Matching objects must satisfy all of the specified label constraints β€” every single one, no skipping, periodt.

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

these are the hand-me-downs from the parent command, and honestly they ate πŸ“

  • --as="" β€” username to impersonate for the operation. User could be a regular user or a service account in a namespace. main character energy but borrowed πŸ’€
  • --as-group=[] β€” group to impersonate for the operation. this flag can be repeated to specify multiple groups β€” stack 'em like bracelets 🫢
  • --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 β€” like, actually insecure, not "insecure" in a cute way. be so for real before you flip this one 😭
  • --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. picky king behavior πŸ‘‘
  • -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). collect the whole set, why not πŸŽ€
  • --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 β€” infinite patience, the ultimate soft girl trait 🌸
  • -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. no notes taken, only ✨consequences✨

🌈 EXAMPLE 🌈

# Mark node "foo" as unschedulable
oc adm cordon foo

see how clean that is?? oc adm cordon foo and boom, foo is cordoned. obsessed. πŸ”₯

🧚 SEE ALSO 🧚

oc-adm(1)

(that trailing comma in the original? we don't talk about her πŸ’€)

⭐ HISTORY ⭐

June 2016, Ported from the Kubernetes man-doc generator. vintage. retro. truly the elder emo of man pages πŸ–€


and that's the whole page bestie 🫢 β€” brought to you by Openshift / Openshift CLI User Manuals, dated June 2016. now go cordon something and slay responsibly πŸ’…βœ¨

πŸ“¦ where this page comes from