Yaml changes in K8s to add Query port 8093

So bottom line is are you saying I can’t have query services running alone in one particular node ? this was my actual challenge that I have mentioned in 3rd thread from last .

No you can have query running on its own class of server, that’s not a problem. What is a problem is adding or removing it from an existing class.

It’s a known problem (and has been for a long time) that Couchbase doesn’t expect a load balancer in front of the admin (UI) service. The default configuration will just load balance to all nodes running the data service. As none of these nodes are running the query service you cannot get to that part of the UI. In order to do what you want to do you need to port-forward to a specific node running the service you are interested in. Now 6.5.0 may have finally fixed this, feel free to try 6.5.0-beta2 and see if it solves the issue, the GA should be along fairly soon.

But infact one of the node was running with query services as per the POD’s specification … so not sure I understand when you mean none of these nodes . I can see that node is working is good health and port has been configured and opened to access query service node . Except the challenge being access this from UI and query .
I didn’t try port forward but not sure if this is good option .
To avoid these issue I have to rebuild the cluster adding query services with data which solves the problem but the defeats the purpose of MDS configuration where I want it to be isolated with its own CPU power .
6.5 I haven’t tried but I will check once we are in that position .
thanks

It doesn’t matter if one node is running the query service, the UI service only routes to data nodes. As these don’t have the query service running, you cannot access the query dashboard.

1 Like

Okay … thanks but this are few small small things which is not well documented in CB portal . Clarifying this i n forum is always possible but nice to have those listed well .
thanks