[EKS] [bug]: kubectl logs fails with remote error: tls: handshake failure
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
**Which service(s) is this request for?**
EKS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Unable to fetch container logs. kubectl logs results in 'tls: handshake failure'
`Error from server: Get https://node-ip-address:10250/containerLogs/kube-system/cluster-autoscaler-aws-cluster-autoscaler-75666c49df-qbt8q/aws-cluster-autoscaler: remote error: tls: handshake failure`
**Are you currently working around this issue?**
No
**Additional context**
Anything else we should know?
This is happening in EKS 1.14 prior version EKS 1.13 works as expected.
Issue faced only for ‘kubectl logs’ command other kubectl command work just fine
**Attachments**
[verbose output of kubectl logs](https://github.com/aws/containers-roadmap/files/4320141/kubectl-logs-verbose-output.txt)
Contributor guide
Research direction
Start with the attached verbose kubectl logs output and compare the reported EKS 1.14 behavior with the stated working 1.13 behavior. Reproduce the failure with kubectl logs against the cluster-autoscaler pod and trace the TLS handshake path; done means identifying and validating the relevant service or configuration fix. No repository file or test is named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100