Manual service configuration not read from boostrap.yml about micronaut-kubernetes HOT 8 CLOSED

Yeah, seems like the manual configuration wasn't loaded at all otherwise the manual flag would be true. Please try to not use the list like:

kubernetes:
  client:
    discovery:
      includes:
        - foo-service
      services:
        foo-service:
            port: grpc
            mode: endpoint

from micronaut-kubernetes.

Yeah now it's working and it's loading both endpoints. Thanks

However it only seems to send requests to one of them. I was under the impression the default behaviour should be to do round-robin load-balancing between the endpoints. Is there additional config needed for that?

from micronaut-kubernetes.

yeah it should do round robin if there are more endpoints. try to configure logging to trace for micronaut-kubernetes.

from micronaut-kubernetes.

and thanks I have to fix the documentation

from micronaut-kubernetes.

Sorry for a slow reply.
So I tried to enable trace logging for Kubernetes and I can see this.

Building ServiceInstance for serviceId [foo-service] and URI [http://10.0.0.1:50051]
Building ServiceInstance for serviceId [foo-service] and URI [http://10.0.0.2:50051]

So it's discovering all instances. But I enabled debug logging for grpc as well and I can see logs like these

"[id: 0x39d05f67, L:/{ip-and-port-of-calling-service} - R:/10.0.0.1:50051] OUTBOUND DATA: streamId=9 padding=0 endStream=true length=21 bytes=00000000100a0532333934301207535448502d5345"

All the calls I do go towards the IP of a single instance, there are never any calls made towards the other.
So it doesn't seem like there is any load-balancing being performed. 🤔

I can also see this in the logs

"Registering singleton bean io.micronaut.http.client.DefaultLoadBalancerResolver@38f57b3d for type [io.micronaut.http.client.LoadBalancerResolver] using bean key io.micronaut.http.client.DefaultLoadBalancerResolver" 
"Finding candidate beans for type: class io.micronaut.http.client.loadbalance.ServiceInstanceListLoadBalancerFactory"
"Finalized bean definitions candidates: [Definition: io.micronaut.http.client.loadbalance.ServiceInstanceListLoadBalancerFactory]"
"Found concrete candidate [Definition: io.micronaut.http.client.loadbalance.ServiceInstanceListLoadBalancerFactory] for type: io.micronaut.http.client.loadbalance.ServiceInstanceListLoadBalancerFactory "

Shouldn't it pick the DiscoverClientLoadBalancer here?

from micronaut-kubernetes.

By default all loadbalancers are RoundRobin kind. However based on the context of execution it may always start with fresh list of service instances. I'll try to look at this. Anyway, if you don't want to use client side loadbalancing, use the discovery mode Service -> https://micronaut-projects.github.io/micronaut-kubernetes/latest/guide/#service-discovery

from micronaut-kubernetes.

Also if you could please open new issue regarding the load balancing. I'll close this one so as resolved. Just copy your comment into new issue I'll handle rest. Thanks!

from micronaut-kubernetes.

Thanks, yes we can close this.

from micronaut-kubernetes.