NVIDIA / NVIDIA/ai-cloud-validation
bug: K8sMultiClusterSameVpcCheck: never provisions or contacts the two clusters it reports on
Open
Nobody has claimed this yet.
bug
kubernetes
priority-1
- Dominant language
- Python
- Stars
- 27
- Forks
- 33
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 28
Description
We don’t actually provision two separate clusters in the same VPC and make sure they come up healthy. The test should attempt to contact the clusters.
Contributor guide
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 at the K8sMultiClusterSameVpcCheck test and inspect how its reported clusters are currently configured. Run the relevant validation test, then make sure it provisions two separate clusters in the same VPC, verifies they become healthy, and attempts to contact both clusters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- infrastructure, networking, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100