Ingress no longer exposing services on port 80
See original GitHub issueI’ve installed microk8s v1.21.0 from latest/edge and added the ingress addon, but microk8s isn’t listening on port 80.
This certainly used to be possible, as it’s been used in various demos. In some discussions about this issue it was suggested that it could be related to reinstalling microk8s (i.e. something isn’t removed on uninstall). I ran sudo snap remove --purge microk8s
and then sudo snap install microk8s --classic --channel=latest/edge
followed by enabling the dns, dashboard, registry, storage and ingress addons.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:31 (11 by maintainers)
Top Results From Across the Web
Ingress no longer exposing services on port 80 #2255 - GitHub
I've installed microk8s v1.21.0 from latest/edge and added the ingress addon, but microk8s isn't listening on port 80.
Read more >Not able to expose port 80 on the host kubernetes ingress
I'm trying to work ingress with kubernetes but it doesn't work. I'm able to deploy everything successfully, but not able to expose port...
Read more >Exposing TCP and UDP services - NGINX Ingress Controller
Ingress does not support TCP or UDP services. For this reason this Ingress controller uses the flags --tcp-services-configmap and --udp-services-configmap ...
Read more >I have deployed pods withs its service and I am getting
I have deployed pods withs its service and I am getting: failed to connect to port 80 · check if port 80 is...
Read more >Installing NGINX Ingress Controller - Documentation
The port range is limited to 30000-32767, so you cannot expose commonly used ports like 80 or 443 with NodePort. LoadBalancer is a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
inspection-report-20210709_142658.tar.gz
FYI, for support of 21.04 and later, microk8s inspect should use “ss” and “ip” commands instead of ifconfig and netstat.
A reboot would simply ensure that there are no leftover iptables rules, network namespaces/interfaces etc. Glad to see that it worked!