# Failing to get external address on ingress rules and metallb

**URL:** <https://discuss.kubernetes.io/t/failing-to-get-external-address-on-ingress-rules-and-metallb/32462>\
**Category:** microk8s\
**Tags:** network\
**Created:** [May 31, 2025, 2:47am UTC](https://discuss.kubernetes.io/t/failing-to-get-external-address-on-ingress-rules-and-metallb/32462 "2025-05-31T02:47:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sam\_Stephens](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/sam_stephens/32/16855_2.png) [@Sam\_Stephens](https://discuss.kubernetes.io/u/Sam_Stephens)\
**Post date:** [May 31, 2025, 2:47am UTC](https://discuss.kubernetes.io/t/failing-to-get-external-address-on-ingress-rules-and-metallb/32462/1 "2025-05-31T02:47:40Z")

</div>

Hi … Very much a novice here … Trying to break through a sticking point in my microk8s exploration/learning.

I have set up 3 pi4s as Ubuntu server 24.04 LTS and deployed a microk8s ha cluster to them. I have metallb and ingress add-ons active.

I have set up metallb and it gets the first address from the range defined but when setting up/configuring the dashboard ingress rules it always gets allocated 127.0.0.1 rather than an external address.

I have disabled/enabled everything a few times and even gone all the way back to reimagine the Pis with clean installs and starting from scratch but I get back to the same sticking point.

Hopefully someone can point me to a missed step or parameter or something as chatgpt and copilot have not got me over the line.

The next milestone I want to achieve is access to the dashboard from the other PCs / devices on my local network.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Sam\_Stephens](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/sam_stephens/32/16855_2.png) [@Sam\_Stephens](https://discuss.kubernetes.io/u/Sam_Stephens)\
**Post date:** [June 9, 2025, 10:06am UTC](https://discuss.kubernetes.io/t/failing-to-get-external-address-on-ingress-rules-and-metallb/32462/2 "2025-06-09T10:06:45Z")

</div>

after much removal and re-application I have now got the dashboard service accessible from outside the cluster but I am not entirely confident of the relationship between all the elements and am struggling to now expose the next service I am trying to deploy in the form of Home Assistant Server.

I have metallb working now and allocating IPs so will close this.