Expose vmstorage to vmselect present in another cluster

[nbvishwa]

I'm running a full scale vmselect, vmagent, vminsert, vmstorage in one of the cluster.
Now I have created another K8 cluster. So I want to re-deploy all the components in the new cluster.
But I want my vmselect in new selector to query from vmstorage of the old cluster.

Hence I was looking for exposing the vmstorage (stateful set) by each service for each pod & having ingress for the same.

My question is that is this possible to achieve?

[f41gh7]

Hello,
It seems, that there is no good way for kubernetes based deployments. You have to configure cross-cluster connectivity and make all vmstorage pods accessible for vmselect from new cluster.

But we're working on new feature - vmselect -> vmselect communication.

In this case, you can expose vmselect from old cluster as nodePort and add it to the vmselect at new cluster as storageNode.

It should be available at the next release.

[valyala]

FYI, the upcoming release will contain the ability to query vmselect nodes from another vmselect nodes - see these docs. In the mean time it is possible to build cluster components of VictoriaMetrics from the latest commit in cluster branch according to these docs and test this functionality.

[valyala]

vmselect can query other vmselect nodes in multi-level setup starting from v1.79.0. Closing this feature request as done.