OC-ADM-WAIT-FOR-STABLE-CLUSTER(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

💅 oc adm wait-for-stable-cluster — like, the manual page, bestie

okay so this is oc adm from the OC ADM(1) manual, dated June 2016, and the star of the show today is wait-for-stable-cluster. she's a patient queen. let's get into it 🫶

✨ NAME ✨

oc adm wait-for-stable-cluster — literally just sits there and waits for your platform operators to stop being chaotic and become stable. main character patience energy 💅

🌸 SYNOPSIS 🌸

oc adm wait-for-stable-cluster [OPTIONS]

🦋 DESCRIPTION 🦋

okay so picture this: you're waiting for every single one of your OCP v4 clusteroperators to report Available=true, Progressing=false, and Degraded=false. that's the whole vibe check. that's it. that's the command. she waits until all of them are slaying at the same time ✨

🎀 OPTIONS 🎀

  • --minimum-stable-period=0 — the minimum duration you need before the cluster counts as stable. ngl the default value says 0 but the default behaviour is 5 minutes. iconic of her to keep us guessing 😭
  • --timeout=0 — how long before the command gives up and times out. the default here is 1 hour, bestie. she's not gonna wait forever 🕐

👑 OPTIONS INHERITED FROM PARENT COMMANDS 👑

these are the hand-me-downs from the parent command and they are, honestly, a lot. but they're all yours 💜

  • --as="" — username to impersonate for the operation. 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. stack 'em 🫶
  • --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 is genuinely the path. no we don't know why either 💀
  • --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're opting 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, bestie. like actually. be careful with this one 🙈
  • --kubeconfig="" — path to the kubeconfig file to use for CLI requests.
  • --kuberc="" — path to the kuberc file to use for preferences. you can turn this off by exporting the KUBECTL_KUBERC=false feature gate, or by turning off the feature with 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 the 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. she'll wait forever, lowkey 🕰️
  • -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.
  • --warnings-as-errors=false — treat warnings received from the server as errors and exit with a non-zero exit code. strict queen behaviour 👑

🌈 EXAMPLE 🌈

fr fr here's how you actually use her:

# Wait for all cluster operators to become stable
oc adm wait-for-stable-cluster

# Consider operators to be stable if they report as such for 5 minutes straight
oc adm wait-for-stable-cluster --minimum-stable-period 5m

⭐ SEE ALSO ⭐

🧚 HISTORY 🧚

June 2016 — ported from the Kubernetes man-doc generator. vintage. retro. a little bit legendary, honestly 🎀

and that's the whole thing, bestie! this page comes to you from Openshift CLI User Manuals, version Openshift, dated June 2016 — go forth and wait for stability, you've got this 💖✨

📦 where this page comes from