tunnel-client "Failed to connect to proxy" errors about inlets-operator HOT 6 CLOSED

Hi @juan-lee thank you for getting in touch.

What Kubernetes distribution are you using?

I've used KinD, k3s, kubeadm, and k3d successfully without issue.

If you suspect issues with the control-port, you can edit the server's systemd unit file to use --control-plane 8080 and the client's connection URL to point to that port.

Want to give that a try?

Alex

from inlets-operator.

https://github.com/alexellis/inlets#bind-a-different-port-for-the-control-plane

from inlets-operator.

Steps to Reproduce (for bugs)

Quoting the blog post for this isn't helpful because it clearly works for around half a dozen people already and there's a video showing it too.

Could you give more info? i.e.

## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->

* inlets version, find via `kubectl get deploy inlets-operator -o wide`


* Kubernetes distribution i.e. minikube v0.29.0., KinD v0.5.1, Docker Desktop:


* Kubernetes version `kubectl version`:


* Operating System and version (e.g. Linux, Windows, MacOS):


* Cloud provisioner: (DigitalOcean.com / Packet.com)

from inlets-operator.

Can you try the add-gc branch and the custom build I made - I'm assuming you're using KinD?

from inlets-operator.

@alexellis I confirmed the code in master now works as advertised. I actually got it working for myself while building a proof-of-concept azure container instance provisioner. I just discovered inlets yesterday on @lachie83's recommendation. Thanks for sharing and great work! I'd love to help out if you're open to it.

from inlets-operator.

It's merged into master now and ready to go, if you want to try again.

Happy to review your PR this week 👍

Delete is now implemented too.

Alex

from inlets-operator.