kubectl logs command doesn't show logs from all the pods when using label selector

[blessedwithsins]

What happened: I'm using kubectl logs command to get the logs of multiple pods of same application using labels. However, it doesn't give logs from all the pods.

What you expected to happen: I should be able to use the -f/--follow option to get the logs from all the pods and use grep/awk with it.

How to reproduce it (as minimally and precisely as possible):

Running multiple replicas of a deployment, try to get the logs using label selector.

Anything else we need to know?: NA

Environment:

• Kubernetes client and server versions (use kubectl version): v1.29.0
• Cloud provider or hardware configuration: GCP
• OS (e.g: cat /etc/os-release):

NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

[ardaguclu]

Are you saying that this usage pattern https://github.com/kubernetes/kubernetes/blob/9e555875e79f60a238952e91e91f79f32c053f9c/staging/src/k8s.io/kubectl/pkg/cmd/logs/logs.go#L77 does not work?

[blessedwithsins]

Are you saying that this usage pattern https://github.com/kubernetes/kubernetes/blob/9e555875e79f60a238952e91e91f79f32c053f9c/staging/src/k8s.io/kubectl/pkg/cmd/logs/logs.go#L77 does not work?

This one works. Is it mandatory to use --all-containers=true to fetch the logs? IMHO it should work without that as well if I'm using label selector.

[sftim]

Maybe you meant kubectl logs deployment/examplename --all-pods=true --follow? --all-containers has a different effect.

[sftim]

/triage needs-information

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale