OC-ADM-POD-NETWORK(1)

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

πŸ’… OC ADM(1) β€” pod network shenanigans, but make it admin

okay so bestie, quick vibe check: this is page one of the OC ADM manual (like, the actual man page, dated June 2016, living under the OpenShift CLI User Manuals umbrella). It's the little landing pad for all the pod-network admin stuff. Pull up a chair πŸŽ€


✨ NAME ✨

oc adm pod-network β€” literally just "Manage pod network". That's the whole assignment. πŸ’…


🌸 SYNOPSIS 🌸

oc adm pod-network [OPTIONS]

πŸ¦‹ DESCRIPTION πŸ¦‹

Manage pod network in the cluster. Yes that's the official line and yes it's giving "we said what we said."

This command provides common pod network operations for administrators. Think of it as the group chat your cluster's networking lives in β€” it's the parent command, so the actual doing happens in its subcommands (peep SEE ALSO, iykyk πŸ‘€).


πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

these come from the parent command, so they're not technically hers, but she's absolutely carrying them and you should know every single one:

  • --as="" β€” Username to impersonate for the operation. User could be a regular user or a service account in a namespace. (yes bestie, you can be literally anyone, main character energy πŸ”₯)
  • --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. (the path is wild, I know, but that's literally what it says β€” do not @ 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. ⚠️ like, insecure insecure. fr fr be careful with this one.
  • --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. no more "lol it's just a warning" energy πŸ’€

πŸ’œ SEE ALSO πŸ’œ

go off, sibling commands, we love a linked list of icons:


🧚 HISTORY 🧚

June 2016 β€” Ported from the Kubernetes man-doc generator. a vintage moment, honestly, she's been serving since 2016 ⭐


🌈 that's the whole page bestie, no cap. every flag, every default, every path β€” all accounted for. go forth and manage that pod network responsibly πŸ‘‘

and that's the sign-off cuties: this is from Openshift β€” the Openshift CLI User Manuals β€” page OC ADM(1), June 2016 era. periodt. πŸ’– πŸ¦‹ πŸ“

πŸ“¦ where this page comes from