OC-ROLLOUT-RESUME(1)

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

✨ oc rollout resume β€” bestie edition ✨

okay so real talk, the manual name is oc rollout resume (it lives in the OC ROLLOUT(1) family, June 2016 vibes, iykyk) and honestly? it's giving "un-pause the thing" and we love that for us πŸ’…

🌸 NAME 🌸

oc rollout resume β€” resume a paused resource. that's it. that's the whole job. iconic.

πŸŽ€ SYNOPSIS πŸŽ€

oc rollout resume [OPTIONS]

πŸ¦‹ DESCRIPTION πŸ¦‹

Resume a paused resource. periodt.

here's the tea though, bestie: paused resources will not be reconciled by a controller. like, at all. they're just sitting there, frozen, not living their truth 😭. by resuming a resource, we allow it to be reconciled again β€” the controller can finally do its little thing and everyone's happy 🫢.

heads up: currently only deployments support being resumed. so don't come for me if your other resources aren't about that life.

⭐ OPTIONS ⭐

  • --allow-missing-template-keys=true β€” if true, ignore any errors in templates when a field or map key is missing in the template. lowkey only applies to golang and jsonpath output formats, ngl.
  • --field-manager="kubectl-rollout" β€” name of the manager used to track field ownership. yes it's the whole main character of field ownership ✨.
  • -f, --filename=[] β€” filename, directory, or URL to files identifying the resource to get from a server.
  • -k, --kustomize="" β€” process the kustomization directory. 🚨 this flag can't be used together with -f or -R, so pick a lane bestie.
  • -o, --output="" β€” output format. one of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). so many options, so little time πŸ’€.
  • -R, --recursive=false β€” process the directory used in -f, --filename recursively. useful when you want to manage related manifests organized within the same directory. very "let me get the whole group chat" energy πŸ™ˆ.
  • -l, --selector="" β€” selector (label query) to filter on, supports =, ==, !=, in, notin. (e.g. -l key1=value1,key2=value2,key3 in (value3)). matching objects must satisfy all of the specified label constraints β€” no partial slay allowed πŸ”₯.
  • --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]. fancy.

πŸ’œ OPTIONS INHERITED FROM PARENT COMMANDS πŸ’œ

these aren't even yours, they're just handed down like family heirlooms πŸŽ€:

  • --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. yes that path is real, 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 β€” dramatic but true, be careful babes.
  • --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. patience is a virtue ✨.
  • -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. strict queen behavior πŸ‘‘.

🌈 EXAMPLE 🌈

# Resume an already paused deployment
oc rollout resume deployment/nginx

look at her go. nginx said "un-pause me" and we said "say less" πŸ’–

🧚 SEE ALSO 🧚

πŸ“ HISTORY πŸ“

June 2016, Ported from the Kubernetes man-doc generator. vintage. retro. a classic πŸ’…


okay that's the whole page bestie, you're officially educated πŸ“šβœ¨ β€” this gem comes from the Openshift CLI User Manuals, Openshift source, dated June 2016 (the OC ROLLOUT(1) era, we stan a nostalgic footer πŸŽ€). now go resume something and slay πŸ¦‹πŸ’œ

πŸ“¦ where this page comes from