OC-ADM-UPGRADE-CHANNEL(1)

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

πŸ’… oc adm upgrade channel

okay so bestie, welcome to the oc adm upgrade channel page β€” that's the command, and it lives in the Openshift CLI User Manuals (the manual's literally named OC ADM UPGRADE(1) if you were wondering πŸŽ€). June 2016 vintage, iconic, we love a retro queen.


✨ NAME ✨

oc adm upgrade channel β€” Set or clear the update channel πŸ¦‹


🌸 SYNOPSIS 🌸

oc adm upgrade channel [OPTIONS]

πŸ’– DESCRIPTION πŸ’–

Set or clear the update channel. yes that's the whole vibe.

This command will set or clear the update channel β€” and that matters, because the channel impacts the list of updates recommended for the cluster. like, it's the thing that tells your cluster which update menu to scroll through πŸ“œβœ¨

If the desired channel is empty, the command will clear the update channel. but listen β€” if there's a list of acceptable channels and your current update channel is in that list, you must pass --allow-explicit-channel to let the channel clear actually proceed. no sneaky clearing, bestie πŸš«πŸ’…

If the desired channel is not empty, the command will set the update channel to it. and if there's a list of acceptable channels and the desired channel is not in that list, you must pass --allow-explicit-channel to let the channel change go through. the gatekeeping is real, but it's for your own good 🫢


πŸ‘‘ OPTIONS πŸ‘‘

  • --allow-explicit-channel=false β€” Change the channel, even if there is a list of acceptable channels and the desired channel is not in that list. (this is your "let me in, i know what i'm doing" pass πŸ”₯)

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these are the ones you didn't ask for but got anyway, and honestly? they ate πŸ’€

  • --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
🫢 tiny heads-up, bestie: --insecure-skip-tls-verify=false is fine as-is, but flipping it to true means the server's certificate will not be checked for validity, and that will make your HTTPS connections insecure. no cap, that's a real security thing, not a vibe thing πŸ’€

🧚 SEE ALSO 🧚

go read the parent page, it's giving main character energy πŸ‘‘


⭐ HISTORY ⭐

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


and that's the page!! πŸ’œ brought to you by Openshift β€” Openshift CLI User Manuals β€” dated June 2016 🌸 mwah, slay, go change a channel responsibly πŸŽ€βœ¨

πŸ“¦ where this page comes from