Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

NodePort restrictions?

See original GitHub issue

Please run microk8s.inspect and attach the generated tarball to this issue.

We appreciate your feedback. Thank you for using microk8s. I want to expose my cluster in a single-node to external access and use nodePort for that purpose. However, it restricts port range to start from 30000. Is there any good reason for that? How can I change that to default HTTP and HTTPS ports? Thanks!

Issue Analytics

State:
Created 5 years ago
Comments:12 (11 by maintainers)

Top GitHub Comments

3reactions

ktsakalozoscommented, Jan 20, 2019

@khteh, you will need to add the --service-node-port-range argument to /var/snap/microk8s/current/args/kube-apiserver and then sudo systemctl restart snap.microk8s.daemon-apiserver.

In respect to security, I am not sure how and to whom MicroK8s will be exposed, but you should be aware that MicroK8s does not take any action to protect its endpoints (eg port 8080). Some of those security concerns will be addressed in the upcoming releases as they are addressed by https://github.com/ubuntu/microk8s/pull/88 . Have a look at the PR as it describes what ports are left open .

0reactions

stale[bot]commented, Apr 4, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.