OC-ADM-WAIT-FOR-NODE-REBOOT(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

💻 oc adm wait-for-node-reboot — the "did my nodes actually reboot??" checker 💅

okay so bestie, welcome to the OC ADM manual ✨ this page is all about oc adm wait-for-node-reboot, and it's giving "I just rebooted a whole pool of machines and now I need to know when they're back" energy. no cap.

🌸 NAME 🌸

oc adm wait-for-node-reboot — literally waits for nodes to reboot after you run oc adm reboot-machine-config-pool. that's the whole vibe 🫶

✨ SYNOPSIS ✨

oc adm wait-for-node-reboot [OPTIONS]

💖 DESCRIPTION 💖

okay so real talk: oc adm wait-for-node-reboot waits for nodes to reboot after running oc adm reboot-machine-config-pool. you kick off a reboot, then you park here and wait for the glow-up to finish. iconic behavior, honestly 🔥

🎀 OPTIONS 🎀

  • --all=false — select all resources in the namespace of the specified resource types. default is false, so it's not doing the most unless you tell it to 💅
  • --field-selector="" — selector (field query) to filter on. supports =, ==, and !=. example: --field-selector key1=value1,key2=value2. heads up: the server only supports a limited number of field queries per type, so don't go wild 🙈
  • -f, --filename=[] — identifying the resource. yes bestie, you can point it at a file. the brackets mean it's a list vibe.
  • --reboot-number=0 — if unset, the current reboot numbers are used. if specified, any node at or beyond that reboot number is considered complete. default is 0 ⭐
  • -R, --recursive=true — process the directory used in -f, --filename recursively. useful when you want to manage related manifests organized within the same directory. default is true, so it's already in its recursive era 🌀
  • -l, --selector="" — selector (label query) to filter on. supports =, ==, and !=. example: -l key1=value1,key2=value2. use this to pick exactly which nodes you're stalking 👀

🦋 OPTIONS INHERITED FROM PARENT COMMANDS 🦋

these are the hand-me-downs from the parent command. still important, still slaying 💜

  • --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. that path is literally what it says, don't @ me 😭
  • --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 — highkey do not recommend unless you know exactly what you're doing 💀
  • --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). default is none 🧚
  • --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. default is "0" ⏳
  • -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. spicy 🌶️

🌈 EXAMPLE 🌈

okay bestie, here are the actual examples. copy them exactly, they're precious:

# Wait for all nodes to complete a requested reboot from 'oc adm reboot-machine-config-pool mcp/worker mcp/master'
oc adm wait-for-node-reboot nodes --all

# Wait for masters to complete a requested reboot from 'oc adm reboot-machine-config-pool mcp/master'
oc adm wait-for-node-reboot nodes -l node-role.kubernetes.io/master

# Wait for masters to complete a specific reboot
oc adm wait-for-node-reboot nodes -l node-role.kubernetes.io/master --reboot-number=4

see how clean that is? ate and left no crumbs 👑

👀 SEE ALSO 👀

📜 HISTORY 📜

June 2016, ported from the Kubernetes man-doc generator. a whole vintage moment 🍓

and that's the page, bestie! this manual is from the Openshift CLI User Manuals, version date June 2016, and the source is Openshift. mwah, go reboot some nodes responsibly 💋✨

📦 where this page comes from