lerminou
commented
4 months ago While checking the code, with the log line, the log "no ipv4 found" is only in a method to set a public LB, I created my LB with the private network only, so that's the issue.
It works when setting the service.beta.kubernetes.io/scw-loadbalancer-private: "true" annotation.
I thought is was useless to set this annotation because the LB is externally managed
I'm using a Kapsule cluster 1.30. I want to use a single load balancer for two services on different ports within a private network, mainly to reduce costs.
To achieve this, I'm using the experimental annotation service.beta.kubernetes.io/scw-loadbalancer-externally-managed.
While this does create the load balancer frontend and backend correctly on the Scaleway API, the service external IP remains stuck in the pending state.
If I remove the annotation, a new load balancer is created for each service, and the external IP is set to a private IP.
Do you have any ETA for the stability of this annotation?
I found this log on scaleway cockpit: but my LB has an private ipv4 address
1 loadbalancers.go:206] error making loadbalancer status for service loki/loki-stack-gateway: no ipv4 found for lb lb-monitoring-private