From 8c5cfab116ab634636f7746017b6d3c17a18df26 Mon Sep 17 00:00:00 2001 From: Traci Morrison Date: Wed, 24 Jan 2018 13:43:26 -0500 Subject: [PATCH] Changed thawed to thwarted --- admin_guide/high_availability.adoc | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/admin_guide/high_availability.adoc b/admin_guide/high_availability.adoc index 688356c5fdad..634dc05636c7 100644 --- a/admin_guide/high_availability.adoc +++ b/admin_guide/high_availability.adoc @@ -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: