OC(1)

📦
version 4.22.0 · 2 versions
, in nixpkgs unstable

💅 OC(1) — the openshift CLI girlies' manual 💅

okay so real talk, this is the oc manual page, and today we're doing the logs glow-up. It's from June 2016 bestie, so she's vintage but she still ate. Let's go ✨

🌸 NAME 🌸

oc logs — print the logs for a container in a pod. literally just vibes and output. 🫶

🎀 SYNOPSIS 🎀

oc logs [OPTIONS]

🦋 DESCRIPTION 🦋

Okay so picture this: you wanna print the logs for a resource. That's the whole game, no cap.

The supported resources are builds, build configs (bc), deployment configs (dc), and pods. Iconic lineup honestly.

Here's the tea though — when a pod is specified and it has more than one container, you gotta name that container with -c. Otherwise it's giving "which one???" 😭 And when a build config or deployment config is specified, you can peek at the logs for a particular version of it via --version. Obsessed with the precision.

If your pod is failing to start, you may need to use the --previous option to see the logs of the last attempt. She's not being dramatic, she's being accurate. 💀

✨ OPTIONS ✨

  • --all-containers=false — get all containers' logs in the pod(s). all of them. the whole squad. 👑
  • --all-pods=false — get logs from all pod(s). Oh and heads up, this sets prefix to TRUE. automatic. you're welcome. 💅
  • -c, --container="" — print the logs of this container. name your container, bestie, don't leave her guessing.
  • -f, --follow=false — specify if the logs should be streamed. yes queen, keep it flowing. 🌊
  • --ignore-errors=false — if watching / following pod logs, allow for any errors that occur to be non-fatal. like, it's fine, we move. 🙈
  • --insecure-skip-tls-verify-backend=false — skip verifying the identity of the kubelet that logs are requested from. In theory, an attacker could provide invalid log content back. You might want to use this if your kubelet serving certificates have expired. ⚠️ real warning, not a cute one — this one's giving risky.
  • --limit-bytes=0 — maximum bytes of logs to return. Defaults to no limit. free rein, no cap (literally). 🔥
  • --max-log-requests=5 — specify maximum number of concurrent logs to follow when using by a selector. Defaults to 5. five little streams running in parallel, slay.
  • --pod-running-timeout=0 — the length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running. patience is a virtue bestie ⏳
  • --prefix=false — prefix each log line with the log source (pod name and container name). receipts included. 🧾
  • -p, --previous=false — if true, print the logs for the previous instance of the container in a pod if it exists. digging up the past, respectfully.
  • -l, --selector="" — selector (label query) to filter on, supports '=', '==', '!=', 'in', 'notin'. (e.g. -l key1=value1,key2=value2,key3 in (value3)). Matching objects must satisfy all of the specified label constraints. all of them. no partial credit. 💯
  • --since=0 — only return logs newer than a relative duration like 5s, 2m, or 3h. Defaults to all logs. Only one of since-time / since may be used. pick a lane, babe. 🚗
  • --since-time="" — only return logs after a specific date (RFC3339). Defaults to all logs. Only one of since-time / since may be used. same rule, different flag. 🤝
  • --tail=-1 — lines of recent log file to display. Defaults to -1 with no selector, showing all log lines otherwise 10, if a selector is provided. read that twice, it's a whole conditional situation. 📖
  • --timestamps=false — include timestamps on each line in the log output. time is real. ⏰
  • --version=0 — view the logs of a particular build or deployment by version if greater than zero. throwback era, but make it versioned. 🕰️

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these came from the parent commands, we're just borrowing them, sharing is caring 💜

  • --as="" — username to impersonate for the operation. User could be a regular user or a service account in a namespace. main character energy, but borrowed. 🎭
  • --as-group=[] — group to impersonate for the operation, this flag can be repeated to specify multiple groups. stack 'em.
  • --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. yes that's the actual path, we don't make the rules. 🏠
  • --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. keep her safe 🔐
  • --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. ⚠️ read it again. yeah. insecure 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. matchy matchy 🪞
  • -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. zero = infinite patience, she will wait forever 😭
  • -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. 🤫 don't share her.
  • --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. strict queen. 💀

🍓 EXAMPLE 🍓

# Start streaming the logs of the most recent build of the openldap build config
oc logs -f bc/openldap

# Start streaming the logs of the latest deployment of the mysql deployment config
oc logs -f dc/mysql

# Get the logs of the first deployment for the mysql deployment config. Note that logs
# from older deployments may not exist either because the deployment was successful
# or due to deployment pruning or manual deletion of the deployment
oc logs --version=1 dc/mysql

# Return a snapshot of ruby-container logs from pod backend
oc logs backend -c ruby-container

# Start streaming of ruby-container logs from pod backend
oc logs -f pod/backend -c ruby-container

^^ that's the whole tutorial bestie, copy paste and thrive 🫶✨

🧚 SEE ALSO 🧚

oc(1), — that's the one and only reference, go say hi to the main page 💖

👑 HISTORY 👑

June 2016, Ported from the Kubernetes man-doc generator — she's a port, she's a legend, she's been here since 2016 and she's still serving. 💅

okay that's the whole page! and for the cute sign-off: this masterpiece came from Openshift — Openshift CLI User Manuals — dated June 2016, and honestly? still iconic. bye bestie, go stream some logs 🌈💖🎀
📦 where this page comes from