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
In certain cases we need to have a node pool that needs to have FIPs assigned (for our use case internal FIPs only).
Internal traffic should use FIP as an outgoing IP. They could random, no need to keep on node upgrade.
External traffic should still use router external IP.
This node pool could be shared with any other pods. Our deployment will have specific node selector for such nodes.
Would be great if this could be done automatically using kubernikus API.
UPD: the independent per-node-pool private network with its own router would be nice as well.
LB is incoming traffic, the request doesn't relate to it.
The requirement is already in the main message: we want internal outgoing traffic to have per-node FIP. Currently all outgoing traffic has router external IP.
In certain cases we need to have a node pool that needs to have FIPs assigned (for our use case internal FIPs only).
Internal traffic should use FIP as an outgoing IP. They could random, no need to keep on node upgrade.
External traffic should still use router external IP.
This node pool could be shared with any other pods. Our deployment will have specific node selector for such nodes.
Would be great if this could be done automatically using kubernikus API.
UPD: the independent per-node-pool private network with its own router would be nice as well.
cc @BugRoger @databus23
The text was updated successfully, but these errors were encountered: