pingcap / pingcap/docs-tidb-operator
DNS not resolved
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 52
- Forks
- 129
- Avg merge
- 12m
- Merged PRs (30d)
- 2
Description
File: /master/en/build-multi-aws-eks.md
i created EKS Cluster done with peering Telnet working, but DNS not resolved
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with master/en/build-multi-aws-eks.md and review the multi-AWS EKS networking and DNS steps around the reported setup. Reproduce or investigate the unresolved DNS behavior, then document the required configuration or correct the affected instructions; done means DNS resolution works as described and the guide is unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, documentation, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100