-
-
Notifications
You must be signed in to change notification settings - Fork 217
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
Expose Load-balancer port through uPNP #58
Comments
^ earlier testing (needs to put it somewhere) |
I'm adding relevant keywords so this can be better found in Google searches: |
I ran this PoC code (with the router port 22 and a 100s port removal). This is awesome! |
A uPNP CCM could query the network (SSDP) to find out if a node is no longer available (to remove it from the cluster), https://www.electricmonk.nl/log/2016/07/05/exploring-upnp-with-python/ |
Merged as of #96 |
This is technically possible to expose the port mapping to a commercial router so we could:
kubectl expose deployment nginx-deployment --port=18080 --type=LoadBalancer --name=nginx-loadbalancer
The
--port=xxx
will need to be considered for the uPNP endpoint (router)Errors will be hard to handle as it's not something that Kubernetes load-balancers are designed to handle, errors would exist the
kube-vip
pod in the namespace the load-balancer is created in. This is where an end-user would find that the exposed port hasn't made it to the router (such as having an already existing port-mapping created).cc / @displague
The text was updated successfully, but these errors were encountered: