@pavan @DudaNogueira I also tried minikube, and I followed this blog (Achieve Zero-Downtime Upgrades with Weaviate’s Multi-Node Setup | Weaviate). I am unsure if this is already a bit dated (since we have v4 client). I successfully reached step “minikube service weaviate --namespace weaviate” to expose to “outside world”, and it launched http://127.0.0.1:/v1and there was no apparent error anywhere. But if I tried to connect using client v4:
client = weaviate.connect_to_local(‘localhost’, …)
I got errors, and this may be pertinent:
AioRpcError: <AioRpcError of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = “failed to connect to all addresses; last error: UNKNOWN: ipv4:127.0.0.1:50051: Failed to connect to remote host: Connection refused”
debug_error_string = “UNKNOWN:Error received from peer {grpc_message:“failed to connect to all addresses; last error: UNKNOWN: ipv4:127.0.0.1:50051: Failed to connect to remote host: Connection refused”, grpc_status:14, created_time:“2024-11-20T13:31:57.896269-05:00”}”
it seems it says there’s no grpc available. I thought it was mentioned this is used in the client and not REST. So I suspect the blog is missing another step where grpc should also be exposed?