Grpc connection to couchbase

Couchbase Server Kubernetes
1

Hello,

Couchbase and grpc server are deployed on k8s as pods. I have been trying to access couchbase from my grpc server. Response below:

System.AggregateException: One or more errors occurred. (Could not bootstrap - check inner exceptions for details. (Connection refused) (Could not bootstrap with CCCP. (Connection refused)) (Could not bootstrap from configured servers list.))
Couchbase.Configuration.Server.Serialization.BootstrapException: Could not bootstrap - check inner exceptions for details. (Connection refused) (Could not bootstrap with CCCP. (Connection refused)) (Could not bootstrap from configured servers list.)
System.Net.Sockets.SocketException (111): Connection refused

Curl from the same grpc server pod to couch base is happening.

kubectl exec -it grpc-server -- curl demo-couchbase.default:8091
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"><html><head><title>301 Moved Permanently</title></head><body><h1>Moved Permanently</h1><p>The document has moved <a href="http://demo-couchbase.default:8091/ui/index.html>here</a>.</p></body></html>

If anyone accessed couchbase from grpc server or with grpc protocol, could guide us.
Thanks in advance.

2

By grpc server, you mean a program you’ve written that uses the Couchbase SDK and exposes some of your own services through gprc, right?

Couchbase itself does not use grpc between the SDK/client and the cluster. Have a look at the Kubernetes Operator docs for details on network options.

Also, any time you’re having connectivity issues, it’d be good to diagnostically check for lower level details with SDK doctor.. It may not find anything, but it will validate that common connectivity problems aren’t there.

You’ll find pre-built binaries on the release page.

Usually the summary at the end is pretty easy to interpret. If you need help with interpretation, please feel free to post it or a link to it here.