OC(1)

💅 OC(1) — the rollout glow-up, aka oc rollout 🎀

okay so bestie, welcome to the manual page for oc rollout — it's the OpenShift CLI user manual situation, OC(1), and we're about to get into it. June 2016 energy but the facts are timeless, fr fr. ✨

---

✨ NAME ✨

oc rollout — Manage the rollout of a resource 🌈

✨ SYNOPSIS ✨

oc rollout [OPTIONS]

✨ DESCRIPTION ✨

Manage the rollout of one or more resources. The way it just handles the vibes of your rollout? iconic. 👑

Valid resource types include:

• deployments
• daemonsets
• statefulsets
• deploymentConfigs (deprecated) 💀

ngl, deploymentConfigs is marked deprecated right there in the source — so if you're still using it, no cap, it's giving legacy. Use it, but know it's deprecated. 🫶

---

🦋 OPTIONS INHERITED FROM PARENT COMMANDS 🦋

these aren't even oc rollout's own options — they're inherited from the parent command, and the way there's like twenty of them?? main character energy honestly. 🙈

• --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 ✨
• --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 🔥
• --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)
• --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.
• -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

heads up bestie: that --insecure-skip-tls-verify one is literally labeled insecure in the source. it will make your HTTPS connections insecure. so like… know that going in. 😭

---

🍓 EXAMPLE 🍓

okay these are the moments, these examples ate and left no crumbs:

# Roll back to the previous deployment
oc rollout undo deployment/abc

# Check the rollout status of a daemonset
oc rollout status daemonset/foo

# Restart a deployment
oc rollout restart deployment/abc

# Restart deployments with the 'app=nginx' label
oc rollout restart deployment --selector=app=nginx

copy them exactly, they're literally verbatim. iykyk 💅

---

🌸 SEE ALSO 🌸

go read these too, they're the whole friend group:

oc(1), oc-rollout-cancel(1), oc-rollout-history(1), oc-rollout-latest(1), oc-rollout-pause(1), oc-rollout-restart(1), oc-rollout-resume(1), oc-rollout-retry(1), oc-rollout-status(1), oc-rollout-undo(1)

---

💜 HISTORY 💜

June 2016, Ported from the Kubernetes man-doc generator ⭐

---

and that's the whole page, bestie!! 🫶 this whole thing is from the Openshift CLI User Manuals — Openshift, version vibes from June 2016 — and it's the OC(1) page you just read. mwah 💖 🎀 🦋