3 ms·

Great work, this is a problem I did have in the past. What are the differences between this and the Kubernetes nginx ingress controller https://github.com/kube

Great work, this is a problem I did have in the past. What are the differences between this and the Kubernetes nginx ingress controller https://github.com/kubernetes/ingress-nginx https://github.com/kubernetes/ingress-nginx with the nginxes configuration set to listen on nodeport?

e12e 7y ago
It registers, functions and can be managed as a LoadBalancer by kubectl etc?
- kubeisnthard 7y ago
  Clearly so does the software in the submission, as it mentions in the second sentence (full actual non-fragment sentence) in the readme. The difference is that nginx-ingress requires some external access TO nginx still. On the other hand, inlets-operator, argo-ingress-controller, (I'm surprised there's not an ngrok controller too) etc, don't require configuring NAT or external internet access TO nginx due to how inlets/argo work. This makes it incredibly useful for exposing a service running on a laptop behind a firewall, or that roams networks frequently but you wanted a stable endpoint name, etc. Personally, I'd skip the middle man and just deploy an onion hidden service (and do -- for kube services and home services that I'd otherwise NAT punch - they just work. No matter where I take my Pi, if it can hit the internet, my Onions are available.
  - cube2222 7y ago
    Thank you for the explanation! Very appreciated!
  - _frkl 7y ago
    Thanks for the explanation. I don't know much about tor hidden services, and wasn't aware they could be used for this purpose. This goes definitely on my list...
  - e12e 7y ago
    >>> What are the differences between this and the Kubernetes nginx ingress controller >> It registers, functions and can be managed as a LoadBalancer by kubectl etc? > Clearly so does the software in the submission Yes, but nginx ingress controller does not work as a [ed: kubernete] LoadBalancer [it does not dynamically expose services via allocating an IP] . Was that unclear? Nice tip about onion, I'd still love to see an automated LoadBalancer for test/dev setup - this submission is the closest I've seen - but it would be great to have a daemon/container you could give a subnet and have it work as a simple LoadBalancer for k8s. Especially if it supported ipv6, as that is readily available with fully routed addresses. [ed2: looks like metallb might be an alternative: https://metallb.universe.tf/ https://metallb.universe.tf/ ] [ed3: would be great to se an lb implementation that integrated with an overlay network like zerotier or wireguard]
alexellisuk 7y ago
It can work with Nginx Ingress actually, to the point you can even run cert-manager in minikube and live traffic. This is ideal if you're running locally, at home, at work, in a hotel room at a conference, at a customer site. You'll get a public and stable IP. A NodePort is good if you are hosting on public cloud already.
- bloopernova 7y ago
  That's really cool. It's entirely possible I'll have to throw together a "learn k8s by doing" kind of tutorial for coworkers in the future. I'll definitely try to use this because being able to serve live pages to other people would make for a cool demo.

e12e 7y ago

It registers, functions and can be managed as a LoadBalancer by kubectl etc?

kubeisnthard 7y ago
Clearly so does the software in the submission, as it mentions in the second sentence (full actual non-fragment sentence) in the readme. The difference is that nginx-ingress requires some external access TO nginx still. On the other hand, inlets-operator, argo-ingress-controller, (I'm surprised there's not an ngrok controller too) etc, don't require configuring NAT or external internet access TO nginx due to how inlets/argo work. This makes it incredibly useful for exposing a service running on a laptop behind a firewall, or that roams networks frequently but you wanted a stable endpoint name, etc. Personally, I'd skip the middle man and just deploy an onion hidden service (and do -- for kube services and home services that I'd otherwise NAT punch - they just work. No matter where I take my Pi, if it can hit the internet, my Onions are available.
- cube2222 7y ago
  Thank you for the explanation! Very appreciated!
- _frkl 7y ago
  Thanks for the explanation. I don't know much about tor hidden services, and wasn't aware they could be used for this purpose. This goes definitely on my list...
- e12e 7y ago
  >>> What are the differences between this and the Kubernetes nginx ingress controller >> It registers, functions and can be managed as a LoadBalancer by kubectl etc? > Clearly so does the software in the submission Yes, but nginx ingress controller does not work as a [ed: kubernete] LoadBalancer [it does not dynamically expose services via allocating an IP] . Was that unclear? Nice tip about onion, I'd still love to see an automated LoadBalancer for test/dev setup - this submission is the closest I've seen - but it would be great to have a daemon/container you could give a subnet and have it work as a simple LoadBalancer for k8s. Especially if it supported ipv6, as that is readily available with fully routed addresses. [ed2: looks like metallb might be an alternative: https://metallb.universe.tf/ https://metallb.universe.tf/ ] [ed3: would be great to se an lb implementation that integrated with an overlay network like zerotier or wireguard]

alexellisuk 7y ago

It can work with Nginx Ingress actually, to the point you can even run cert-manager in minikube and live traffic. This is ideal if you're running locally, at home, at work, in a hotel room at a conference, at a customer site. You'll get a public and stable IP. A NodePort is good if you are hosting on public cloud already.

bloopernova 7y ago
That's really cool. It's entirely possible I'll have to throw together a "learn k8s by doing" kind of tutorial for coworkers in the future. I'll definitely try to use this because being able to serve live pages to other people would make for a cool demo.