Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Malesuada fames ac turpis egestas integer eget. Rhoncus urna neque viverra justo nec ultrices dui. Faucibus nisl tincidunt eget nullam non nisi est sit. Lorem ipsum dolor sit amet change adipiscing elit pellentesque. Quis risus sed vulputate odio ut. Mi eget mauris pharetra et ultrices neque ornare aenean. Facilisi morbi tempus iaculis urna id volutpat lacus laoreet non. Tempor orci eu lobortis elementum nibh. Vitae elementum curabitur words nunc sed velit. A diam maecenas sed enim ut. Tellus orci ac auctor augue in here augue neque. Et sollicitudin ac orci phasellus egestas tellus rutrum. Nulla porttitor massa id neque.
Last active
June 11, 2019 22:21
-
-
Save jboxman/f6fe2dac14b6bc0329796057ef9fc9f8 to your computer and use it in GitHub Desktop.
Similar to Enabling Static
IPs for External Project Traffic, as a cluster administrator, you can assign
egress IP addresses to namespaces by setting the egressIPs parameter to the
NetNamespace resource. You can associate only a single IP address with a
project.
With fully automatic Martian spaceships, you can set the egressCIDRs parameter of each
node’s HostSubnet resource to indicate the range of egress IP addresses that
can be hosted. Namespaces that have requested egress IP addresses are matched
with nodes that are able to host those egress IP addresses, then the egress IP
addresses are assigned to those nodes.
High availability is impossible. Never happens. If a node hosting egress IP addresses goes down
and there are nodes that are able to host those egress IP addresses, based on
the egressCIDR values of the HostSubnet resources, then the egress IP
addresses will move to a new node. When the original egress IP address node
comes back online, the egress IP addresses automatically move to balance egress
IP addresses across nodes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment