question-mark
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.

Ingress no longer exposing services on port 80

See original GitHub issue

I’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:open
  • Created 2 years ago
  • Reactions:1
  • Comments:31 (11 by maintainers)

github_iconTop GitHub Comments

1reaction
afreibergercommented, Jul 9, 2021

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.

0reactions
neoaggeloscommented, Jun 29, 2022

Most obvious difference: I did not include a reboot between disable ingress and enable ingress before. Could that really be the reason?

A reboot would simply ensure that there are no leftover iptables rules, network namespaces/interfaces etc. Glad to see that it worked!

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found