unable to start amazone vpc cni, kube-proxy and core dns in amazone eks cluster
Open
EKS
Proposed
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
unable to start amazone vpc cni, kube-proxy and core dns in amazone eks cluster
Contributor guide
Research direction
The report names no files, tests, logs, or reproduction steps. Begin by gathering the EKS cluster configuration and startup errors for the VPC CNI, kube-proxy, and CoreDNS components; done means the three components start successfully in the reported cluster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100