Skip to content

[enterprise-3.3] Changed thawed to thwarted #7531

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
1 commit merged into from Feb 2, 2018
Merged

[enterprise-3.3] Changed thawed to thwarted #7531

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions admin_guide/high_availability.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,8 +29,16 @@ For some IP-based traffic services, virtual IP addresses (VIPs) should always be
serviced for as long as a single instance is available. This simplifies the
operational overhead and handles failure cases gracefully.

IMPORTANT: Even though
a service is highly available, performance can still be affected.
[IMPORTANT]
====
Setting up a nodePort is a privileged operation.
====

[IMPORTANT]
====
Even though a service VIP is highly available, performance can still be affected. *keepalived* makes sure that each of the VIPs is serviced by some node in the configuration, and several VIPs may end up on the same node even when other nodes have none. Strategies that externally load balance across a set of VIPs
may be thwarted when ipfailover puts multiple VIPs on the same node.
====

Use cases for high-availability include:

Expand Down