OC-ROLLOUT-LATEST(1)
πΈ OC ROLLOUT LATEST πΈ
okay so bestie, welcome to the oc rollout latest glow-up π
this is your go-to move for kicking off a fresh rollout on a deployment config, and I'm gonna walk you through it like we're texting at 2am π«Ά it lives in the OC ROLLOUT manual (part of the Openshift CLI User Manuals situation, iykyk), and we're gonna make it make sense fr fr β¨
β¨ SYNOPSIS β¨
oc rollout latest [OPTIONS]
π DESCRIPTION π
So like, this command literally starts a new rollout for a deployment config using the latest state from its triggers. That's the whole vibe π
It's the move when you're doing manual rollouts β like you want to be the main character calling the shots π. The manual (no cap) says: if you want full control over running new rollouts, use oc set triggers --manual to disable all triggers in your deployment config. Then whenever you're ready to run a new deployment process, you hit this command to pick up the latest images found in the cluster that are pointed by your image change triggers. It's giving intentional π
π OPTIONS π
--again=falseβ if true, deploy the current pod template without updating state from triggers π--allow-missing-template-keys=trueβ if true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats π₯--dry-run="none"β must be"none","server", or"client". If client strategy, only print the object that would be sent, without sending it. If server strategy, submit server-side request without persisting the resource π¦-o,--output=""β output format, bestie. one of:json,yaml,kyaml,name,go-template,go-template-file,template,templatefile,jsonpath,jsonpath-as-json,jsonpath-fileβ--show-managed-fields=falseβ if true, keep the managedFields when printing objects in JSON or YAML format π--template=""β template string or path to template file to use when-o=go-template,-o=go-template-file. The template format is golang templates [ β¨http://golang.org/pkg/text/template/#pkg-overviewβ© ] π§
π OPTIONS INHERITED FROM PARENT COMMANDS π
--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 β οΈ (like, actually insecure, bestie β be careful)--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 exportingKUBECTL_KUBERC=falsefeature gate or turning off the featureKUBERC=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 π¨
π¦ EXAMPLE π¦
# Start a new rollout based on the latest images defined in the image change triggers
oc rollout latest dc/nginx
# Print the rolled out deployment config
oc rollout latest dc/nginx -o json
π« SEE ALSO π«
π HISTORY π
June 2016, Ported from the Kubernetes man-doc generator π (yes bestie, it's giving vintage)
okay that's the whole page, and honestly? iconic π no cap, every single flag and default and file path is in there exactly as it should be β I would never leave out the boring bits, that's not the vibe π now go forth and roll out those deployments like the main character you are π
Openshift π Openshift CLI User Manuals π OC ROLLOUT(1) β sending you all the good vibes, mwah π«Άβ¨
π¦ where this page comes from
- nixpkgs unstable: openshift 4.22.0-202605222050
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms