Configuring Skupper for Clusters Behind NAT with External IP

[romankudravcev]

Hi everyone,

I'm new to Skupper and might not fully understand everything yet. I want to connect two clusters hosted in an on-premises environment. The challenge I'm facing is that my load balancing IPs are behind a 1-to-1 NAT. This means that the IP I specify in the Skupper configuration is the internal IP, but I need to use the external IP when making requests between clusters.

I’m looking for a way to declare the external IP somewhere in the configuration, so that when one cluster links to the other, it knows where to send the requests. During my search, I came across an issue that seems to address this problem: Skupper PR #1171.

Can someone explain how to use this solution if it's still relevant? Or is there another simple solution to this problem?

Thanks in advance!

[grs]

That feature allows the /etc/hosts file of the router pod to have aliases included. In v1 it is an explicit option. In v2, there is no such option, but you can apply a Deployment skeleton with that section filled in against the skupper-router pod (the controller uses Server Side Apply so there should be no conflict).

[romankudravcev]

Then I mean something different than the issue mentioned. :) I want to change the URL in the token.yaml because the skupper controller uses an internal IP that cannot be reached from outside, which means that I cannot link to the cluster. The host aliases don't really help, as no IP can be entered here as a hostname. I just want to change the ‘skupper.io/url’ in the token to replace the internal IP with the external IP. Is there any other way to do this?