# Repeated nodeAssigned in ingress service events when using metallb

**URL:** <https://discuss.kubernetes.io/t/repeated-nodeassigned-in-ingress-service-events-when-using-metallb/29471>\
**Category:** microk8s\
**Tags:** metallb\
**Created:** [August 22, 2024, 5:32am UTC](https://discuss.kubernetes.io/t/repeated-nodeassigned-in-ingress-service-events-when-using-metallb/29471 "2024-08-22T05:32:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dezmenerefe](https://avatars.discourse-cdn.com/v4/letter/d/f1d935/32.png) [@dezmenerefe](https://discuss.kubernetes.io/u/dezmenerefe)\
**Post date:** [August 22, 2024, 5:32am UTC](https://discuss.kubernetes.io/t/repeated-nodeassigned-in-ingress-service-events-when-using-metallb/29471/1 "2024-08-22T05:32:56Z")

</div>

Hi, we’ve been using MicroK8s since version 1.23 for our production bare-metal server due to its simplicity of installation. However, since version 1.24+, we’ve been unable to get MetalLB working properly. Our service using ingress keeps reconnecting after a certain period, specifically during the `nodeAssigned` events in the ingress service.

Here is the description of our ingress service:

```auto
Name: ingress-service
Namespace: ingress
Labels: <none>
Annotations: <none>
Selector: name=nginx-ingress-microk8s
Type: LoadBalancer
IP Family Policy: SingleStack
IP Families: IPv4
IP: 10.152.183.249
IPs: 10.152.183.249
LoadBalancer Ingress: 10.10.11.240
Port: http 80/TCP
TargetPort: 80/TCP
NodePort: http 31141/TCP
Endpoints: 10.1.14.198:80,10.1.207.196:80
Port: https 443/TCP
TargetPort: 443/TCP
NodePort: https 30296/TCP
Endpoints: 10.1.14.198:443,10.1.207.196:443
Session Affinity: None
External Traffic Policy: Cluster
Events:
  Type Reason Age From Message
  ---- ------ ---- ---- -------
  Normal nodeAssigned 4s (x32 over 73m) metallb-speaker announcing from node "test" with protocol "layer2"

```

We have been following this [tutorial](https://microk8s.io/docs/addon-metallb), but since version 1.24, the `nodeAssigned` events have been occurring randomly. As a result, we had to downgrade to version 1.23 to make it work.

aany idea what’s happening? We tried using the latest version 1.30.3, but the issue still persists.