metallb provided address does not work 100%

[Marian Gasparovic]

I have microk8s charm deployed and then I deploy metallb charm to get external addresses

Provided adress sometimes does not work at all, sometimes it works for a while nad sometimes it works fine for a long time

Here is an example, starting microbot, wget five times in 1 second interval, delete microbot, repeat

# for i in {1..100}; do kubectl apply -f example-microbot-lb.yaml; sleep 3; for j in {1..5}; do timeout 5 wget --quiet 10.244.40.80 -O -|grep hostname; sleep 1; done; kubectl delete -f example-microbot-lb.yaml; sleep 3; done

deployment.apps/microbot-lb created
service/microbot-lb created
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-whclj</p>
Terminated
Terminated
Terminated
Terminated
deployment.apps "microbot-lb" deleted
service "microbot-lb" deleted
deployment.apps/microbot-lb created
service/microbot-lb created
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-x2l4v</p>
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-8r7x5</p>
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-x7rt4</p>
Terminated
Terminated
deployment.apps "microbot-lb" deleted
service "microbot-lb" deleted
deployment.apps/microbot-lb created
service/microbot-lb created
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-j7z7w</p>
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-sqznr</p>
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-sqznr</p>
Terminated
Terminated
deployment.apps "microbot-lb" deleted
service "microbot-lb" deleted
deployment.apps/microbot-lb created
service/microbot-lb created
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-w9n56</p>
Terminated
Terminated
Terminated
Terminated
deployment.apps "microbot-lb" deleted
service "microbot-lb" deleted
deployment.apps/microbot-lb created
service/microbot-lb created
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-xb58h</p>
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-2n7qg</p>
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-xb58h</p>
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-xb58h</p>
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-7ll2z</p>
deployment.apps "microbot-lb" deleted
service "microbot-lb" deleted
deployment.apps/microbot-lb created
service/microbot-lb created
Terminated
Terminated
Terminated
Terminated
Terminated
deployment.apps "microbot-lb" deleted
service "microbot-lb" deleted
deployment.apps/microbot-lb created
service/microbot-lb created
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-7d8xl</p>
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-7d8xl</p>
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-np9wv</p>
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-frhxl</p>
    <p class="centered">Container hostname: microbot-lb-6b9b44b458-frhxl</p>
deployment.apps "microbot-lb" deleted
service "microbot-lb" deleted

Deployed with

description: A charm bundle to deploy MetalLB in Kubernetes
bundle: kubernetes
applications:
  metallb-controller:
    charm: cs:~containers/metallb-controller
    scale: 1
    options:
      iprange: "10.244.40.80-10.244.40.99"
  metallb-speaker:
    charm: cs:~containers/metallb-speaker
    scale: 1

[Marian Gasparovic (marosg)]

The issue was I had everything on oam network. Once I separated default binding to oam-space and cluster binding to internal-space, all works 100% of the time