OC(1)
β¨ 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 togolangandjsonpathoutput formats. forgiving queen energy π--chunk-size=500β return large lists in chunks rather than all at once. pass0to 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 themanagedFieldswhen 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 exportingKUBECTL_KUBERC=falsefeature gate or turning off the featureKUBERC=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
- nixpkgs unstable: openshift 4.22.0-202605222050
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms