aws / aws/aws-cloud-map-mcs-controller-for-k8s
Integration test does not restore original kubectl context
- Dominant language
- Go
- Stars
- 98
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
To recreate:
1. Set up cluster according to CONTRIBUTING.md docs.
2. Run `make integration-suite`, which creates it's own kind cluster and sets its own context.
3. After a successful integration test, if you `make clean` then run `make install` again, you may get this error:
```
The connection to the server localhost:8080 was refused - did you specify the right host or port?
```
Can fix by resetting kubectl context with `kind export kubeconfig --name my-cluster`, but may be beneficial for integration to reset kubectl context for user.
Contributor guide
Research direction
The issue points to CONTRIBUTING.md and the make integration-suite, make clean, and make install targets; start by reading those setup and Makefile entry points to trace when the kind context is selected. Done means a successful integration run followed by cleanup leaves the user's original kubectl context usable for the subsequent install, while preserving the existing cluster setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100