How route traffic to another consul node? about consul-helm

[thisisnotashwin]

hey @Shige99011

In the above case, the IP that the service is registered with Consul has to be the NodeIP (using node ports) and not the cluster IP. That is because there is no way currently for Consul to route traffic to the service. Mesh Gateways currently only work on a Consul federation (in which case you have multiple Consul Servers in different datacenters that are federated together).
I think the above deployment pattern might be unsupported otherwise. 😞

[Shige99011]

Thanks @thisisnotashwin for the info.

So without any routing, I tried to directly access from the service on Node A to the service on Node B via sidecar proxy but it didn't work. Is this expected too?
In this case, it needs to specify the IP of Node B and port(NodePort) to access to the service on Node B, correct? That has worked, I confirmed btw.

on the other hand,
If both nodes have datacenter and run as consul server, the direct access via sidecar proxy works with mesh gateway, right? I saw the feature in the document.

Thanks for your help.

[thisisnotashwin]

In this case, it needs to specify the IP of Node B and port(NodePort) to access to the service on Node B, correct? That has worked, I confirmed btw.

Exactly!! it would need to communicate with the other service with it's public IP

If both nodes have datacenter and run as consul server, the direct access via sidecar proxy works with mesh gateway, right? I saw the feature in the document.

bingo!! you can federate those consul clusters and use the mesh gateways to communicate using them!!

[Shige99011]

Ok, I confirmed it works with the federation and mesh gateway instead of my first deployment pattern. The communication works via sidecar proxy between the nodes!
However I would like to confirm that my first deployment pattern is really not supported.

No problems if it is not supported of course but I just want reliable information because:
On Consul UI of Node A, I could see Node B and the service on Node B. Also the topology from the service on Node A to the service on Node B seemed to be indicated correctly. So I concern that there is just any lack of my configuration for my first deployment pattern.

Thanks for any help.

[Shige99011]

Anyway, I confirmed that the cluster consist of multi nodes works to communicate via sidecar proxy beyond the node without mesh gateway and federation.
To make it, I just configured a kubernetes cluster by multi nodes before Consul configuration. For the my first case, I didn't it. And deployed each pod with node specific by using nodeSelector. That's it.