Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add VPN interference check: HTTP fetch before installing Kubernetes #5426

Closed
tstromberg opened this issue Sep 21, 2019 · 0 comments · Fixed by #5592
Closed

Add VPN interference check: HTTP fetch before installing Kubernetes #5426

tstromberg opened this issue Sep 21, 2019 · 0 comments · Fixed by #5592
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@tstromberg
Copy link
Contributor

tstromberg commented Sep 21, 2019

Here's an idea to address #4302

Add a lightweight HTTP service to our VM that unobtrusively reports system stats, such as load average. As soon as we can confirm SSH access to our VM, and the VM appears to be of the correct version, try accessing this service.

Port 8443 would be ideal for catching the issue, but lets say a nearby port to avoid conflicts.

This would kill two birds with one stone:

  • A lightweight way to gather system metrics without impacting VM load (compared to ssh+uptime command)
  • A way to detect connectivity issues separate from Kubernetes.

If it fails, we could report a very clear message, such as:

Unable to make HTTP requests to the VM (http://<ip>:port). To use minikube, please adjust your firewall or VPN to allow these connections.

We can always add --force to workaround issues with it.

@tstromberg tstromberg added kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/discuss Items for discussion labels Sep 21, 2019
@tstromberg tstromberg removed the triage/discuss Items for discussion label Sep 30, 2019
@tstromberg tstromberg self-assigned this Oct 10, 2019
@tstromberg tstromberg added this to the v1.5.0 milestone Oct 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant