You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to use an egress node in our Kubernetes cluster, but occasionally need to drain the node pool, which results in the loss of the Floating IP.
We use this IP in the firewalls and whitelists of external services that our cluster connects to.
Request
Please allow the specification of an existing Floating IP ID for a node. This would help us avoid losing the IP during maintenance, and reduce the operational overhead when this occurs.
The text was updated successfully, but these errors were encountered:
I never actually looked at the egress gateway, but it's documentation says there's more advanced methods of selecting an exit, rather than "just" the IP address.
Looking at the way this terraform module is set up, it would make sense to either:
Select an existing floating ip, either by IP, label or ID
Create our own floating IP if absent, if desired to do so (selectable by variable)
Description
We want to use an egress node in our Kubernetes cluster, but occasionally need to drain the node pool, which results in the loss of the Floating IP.
We use this IP in the firewalls and whitelists of external services that our cluster connects to.
Request
Please allow the specification of an existing Floating IP ID for a node. This would help us avoid losing the IP during maintenance, and reduce the operational overhead when this occurs.
The text was updated successfully, but these errors were encountered: