Ports in tunnel are not updated when updating the LoadBalancer service about inlets-operator HOT 4 CLOSED

Hi @jsiebens inlets PRO does have the capability to reconfigure, so this is just coming down to the controller's control-loop.

Would you be interested in contributing a fix? You'd have to change the config of the client deployment, which specifies the set of ports.

For the time being as a workaround, update your LB's ports and then delete the tunnel custom resource. The new one created by the operator will have the updated ports.

Alex

from inlets-operator.

Let me know your thoughts.

from inlets-operator.

Hi @alexellis

Deleting the tunnel custom resource as a workaround will indeed create a new one with the updated ports.
But by creating a new exit node, the load balancer will also get a new public IP address, which is a little bit of a pity of the previous address is already configured in other places like DNS records etc.

I will have a look if I can create a PR for this.

Johan

from inlets-operator.

@jsiebens only the tunnel deployment needs to be changed AFAIK, would you still like to work on this PR?

Loop
Detect port change
Update deployment
Tunnel client reconnects, and sets new ports

There will be no change in IP.

Alex

from inlets-operator.