OC-CONFIG-GET-CLUSTERS(1)

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

πŸ’… NAME πŸ’…

bestie you're on the oc config get-clusters page, also known as OC CONFIG(1) if you're being fancy. it literally shows you the clusters defined in your kubeconfig. that's it. that's the whole vibe.


✨ SYNOPSIS ✨

oc config get-clusters [OPTIONS]

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so this command is lowkey iconic in its simplicity. it displays the clusters defined in the kubeconfig. no cap. you run it, it lists clusters. main character energy fr fr.


πŸŽ€ OPTIONS INHERITED FROM PARENT COMMANDS πŸŽ€

these babies are inherited from the parent command, meaning they trickle down to this one. you get them all for free. let's go through them one by one, bestie.

  • --as="" β€” who you're impersonating for the operation. could be a regular user or a service account in a namespace. very demure.
  • --as-group=[] β€” the group you're impersonating. you can repeat this flag to stack up multiple groups. iconic behavior.
  • --as-uid="" β€” the UID you're impersonating for the operation. yes, that's a thing.
  • --as-user-extra=[] β€” extra user info to impersonate. repeat this flag to specify multiple values for the same key. iykyk.
  • --cache-dir="/homeless-shelter/.kube/cache" β€” default cache directory. the path is literally /homeless-shelter/.kube/cache which is a whole vibe.
  • --certificate-authority="" β€” path to a cert file for the certificate authority. secure queen.
  • --client-certificate="" β€” path to a client certificate file for TLS. slay.
  • --client-key="" β€” path to a client key file for TLS. keep it secret, keep it safe.
  • --cluster="" β€” the name of the kubeconfig cluster to use. pick your fighter.
  • --context="" β€” the name of the kubeconfig context to use. another pick-your-fighter moment.
  • --disable-compression=false β€” if true, you're opting out of response compression for all requests to the server. lowkey brave.
  • --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 be careful with this one, no cap.
this is literally a security warning. do not ignore it.
  • --kubeconfig="" β€” use a particular kubeconfig file. not the default one. a particular one. periodt.
  • --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. iykyk.
  • --match-server-version=false β€” require server version to match client version. strict queen behavior.
  • -n, --namespace="" β€” if present, the namespace scope for this CLI request. very mindful.
  • --profile="none" β€” name of profile to capture. one of (none|cpu|heap|goroutine|threadcreate|block|mutex). default is none.
  • --profile-output="profile.pprof" β€” name of the file to write the profile to. default file is profile.pprof.
  • --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 like 1s, 2m, 3h. a value of zero means don't timeout requests. periodt.
  • -s, --server="" β€” the address and port of the Kubernetes API server. finding your 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. no extra effort needed.
  • --token="" β€” bearer token for authentication to the API server. your little key to the kingdom.
  • --user="" β€” the name of the kubeconfig user to use. who dis.
  • --warnings-as-errors=false β€” treat warnings received from the server as errors and exit with a non-zero exit code. dramatic but valid.

πŸ”₯ EXAMPLE πŸ”₯

# List the clusters that oc knows about
oc config get-clusters

⭐ SEE ALSO ⭐

  • oc-config(1) β€” the main character parent page. go check it out bestie.

πŸ’œ HISTORY πŸ’œ

June 2016, ported from the Kubernetes man-doc generator. vintage era fr fr.


this page is brought to you by the Openshift CLI User Manuals, dated June 2016. mwah πŸ’‹

πŸ“¦ where this page comes from