service-node-port-range: 79-32767 is not a sane default

ReSearchITEng / kubeadm-playbook

Fully fledged (HA) Kubernetes Cluster using official kubeadm, ansible and helm. Tested on RHEL/CentOS/Ubuntu with support of http_proxy, dashboard installed, ingress controller, heapster - using official helm charts

https://researchiteng.github.io/kubeadm-playbook/

The Unlicense

592 stars 102 forks source link

service-node-port-range: 79-32767 is not a sane default #85

Closed bkmeneguello closed 4 years ago

bkmeneguello commented 5 years ago

ClusterConfiguration.yml#8 defines service-node-port-range: 79-32767 but this is not a good practice because can cause conflicts with other service ports.

ReSearchITEng commented 4 years ago

Well, the idea is that nginx-controller has to be on 80 and 443 especially for that reason: have k8s the one to hold the web servers. Unfortunately I am not aware of another solution to have few ranges.

ReSearchITEng commented 4 years ago

should anyone modify this range, the nginx controller helm chart port should be also updated in addons.yaml
I am closing, as I don't see other better and intuitive solutin