get-pod-logs doesn't capture logs from multi-container pods
- Dominant language
- Shell
- Stars
- 5
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
```
09:53:42 Error from server: a container name must be specified for pod workflow-e2e, choose one of: [tests artifacts]
09:53:56 Error from server: a container name must be specified for pod heapster-v1.2.0-2328783301-e25p5, choose one of: [heapster heapster-nanny]
09:53:57 Error from server: a container name must be specified for pod kube-dns-v20-b4tah, choose one of: [kubedns dnsmasq healthz]
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the get-pod-logs entry point in the e2e-runner and reproduce the reported errors with multi-container pods such as workflow-e2e, heapster-v1.2.0-2328783301-e25p5, and kube-dns-v20-b4tah. Done means logs are captured without the Kubernetes container-name errors for pods containing multiple containers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100