4 ms·
Also the team randomly decided NodePorts can only[1]: 1. be run in a specific range 2. you can expand that range, but if you do, any port in that range might
by rektide 6y ago
Also the team randomly decided NodePorts can only[1]:
1. be run in a specific range
2. you can expand that range, but if you do, any port in that range might be randomly assigned, so your service might start up on port 80.
Changing alone would make using Kubernetes 10x easier for small operators. But one bomb-throwing curmudgeon drops by with entirely content-free unsubstantiated anger-posting:
> Unless I'm misunderstanding the proposal, it involves unpredictable and difficult to diagnose failure of services, which seems like a complete non-starter to me.
And the small-operators who just want some ability to open http or dns ports get nothing. Maddening beyond belief.
[1] https://github.com/kubernetes/kubernetes/issues/9995 https://github.com/kubernetes/kubernetes/issues/9995
- intricatedetail 6y agoI would like something that would reconfigure Nginx reverse proxy to whatever private ip and port service is given, so that it would work like for big cloud providers without the need of BGP access level to a network.
- manigandham 6y agoHave you seen this: https://www.getambassador.io/docs/latest/topics/install/bare-metal/ https://www.getambassador.io/docs/latest/topics/install/bare...
- intricatedetail 6y agoThis won't work as it doesn't support virtual hosts. For example you cannot provision two services using same port and an IP address. If you have a bare metal server with one IP address you would still have to do e.g. reverse proxy manually which defeats the purpose of having k8s.
- deleted 6y ago[deleted]
- manigandham 6y agoIt eventually made it to the SIG Networking agenda, but it needs people to join the meeting and discuss it. That's the official process for changes now.