Open IBMRob opened 6 years ago
Thanks for the report. Technically I guess we need to expose the kubeadm configuration yaml. We will definitely do it, it's just a matter of time.
/lifecycle frozen
Can this be unfrozen? It would be nice to have 443 on my development machine available.
Requested behavior
Support supplying a range of ports for the nodePort listeners to use. This would enable us to create a service of type nodeport and open up low range port numbers such as 80 and 443 running in Kubenetes.
Current behavior
When creating the service a if you supply a low value nodeport such as 80 or 443, these will not be used btu a random number will be picked in the range 30000-33000
Information
The "--service-node-port-range" flag is used on kube-apiserver (https://kubernetes.io/docs/reference/generated/kube-apiserver/)
Steps to reproduce the behavior
Engine: 17.12.0-ce Kubernetes: v1.8.2