OC(1)

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

✨ OC(1) β€” oc events: the events glow-up ✨

okay bestie, welcome to the oc events manual πŸ’… this is the Openshift CLI User Manuals era, and we're about to read the whole thing together, no skimming, no cap.


🌸 NAME 🌸

oc events β€” list events. that's it. that's the whole gig πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

oc events [OPTIONS]

✨ DESCRIPTION ✨

so it displays events. literally just prints a table of the most important information about events πŸ’–

you can request events for a namespace, for all namespaces, or filtered to only those pertaining to a specified resource. pick your fighter, bestie πŸ‘‘


πŸ’… OPTIONS πŸ’…

  • -A, --all-namespaces=false β€” if present, list the requested object(s) across all namespaces. the namespace in current context is ignored even if specified with --namespace. no crumbs left behind 🧹
  • --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. forgiving queen energy πŸ™ˆ
  • --chunk-size=500 β€” return large lists in chunks rather than all at once. pass 0 to disable. baby steps, we don't need the whole thing at once πŸ“
  • --for="" β€” filter events to only those pertaining to the specified resource. main character filter ✨
  • --no-headers=false β€” when using the default output format, don't print headers. barefaced, no makeup πŸ’„
  • -o, --output="" β€” output format. one of: (json, yaml, kyaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). choose your aesthetic 🌈
  • --show-managed-fields=false β€” if true, keep the managedFields when printing objects in JSON or YAML format. receipts stay visible 🧾
  • --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]. DIY slay πŸ› οΈ
  • --types=[] β€” output only events of given types. picky eater behavior, and honestly valid 🍽️
  • -w, --watch=false β€” after listing the requested events, watch for more events. it's giving "i'm not done here" πŸ‘€

πŸ‘‘ 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. dress-up mode 🎭
  • --as-group=[] β€” group to impersonate for the operation, this flag can be repeated to specify multiple groups. the more the merrier 🫢
  • --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. yes you can stack them πŸ’œ
  • --cache-dir="/homeless-shelter/.kube/cache" β€” default cache directory. that's the literal path, don't come for 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. uncompressed and unbothered πŸ’€
  • --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, that is a real warning, not a vibe ⚠️
  • --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. strict little perfectionist 🀝
  • -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). pick exactly one, we're not doing a combo meal πŸ”
  • --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. patient girly βŒ›
  • -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 warnings tolerated, periodt πŸ”₯

🧚 EXAMPLE 🧚

these are verbatim, copy them exactly, i'm not playing πŸ’–

# List recent events in the default namespace
oc events

# List recent events in all namespaces
oc events --all-namespaces

# List recent events for the specified pod, then wait for more events and list them as they arrive
oc events --for pod/web-pod-13je7 --watch

# List recent events in YAML format
oc events -oyaml

# List recent only events of type 'Warning' or 'Normal'
oc events --types=Warning,Normal

(and yes, "List recent only events" is literally how the original example comment reads β€” i'm keeping it character for character, don't @ me 🀭)


⭐ SEE ALSO ⭐


🌷 HISTORY 🌷

June 2016, Ported from the Kubernetes man-doc generator. vintage but make it cute πŸŽ€


heads up bestie: --insecure-skip-tls-verify is genuinely the dangerous one here β€” it means the server's certificate will not be checked for validity and your HTTPS connections will be insecure. iconic for testing, not for trusting 🫢

and that's the whole page, bestie, we ate πŸ½οΈπŸ’… this was the Openshift CLI User Manuals, June 2016 edition β€” see you in the group chat πŸ˜­βœ¨πŸ¦‹

πŸ“¦ where this page comes from