From 773def6cdc13c2d5f25d7bfe89d11fbd17622ff8 Mon Sep 17 00:00:00 2001 From: Martin Dietze Date: Thu, 22 Feb 2018 15:46:29 +0100 Subject: [PATCH] High Availability guide for kubeadm: text change as proposed by @mattkelly. --- docs/setup/independent/high-availability.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/setup/independent/high-availability.md b/docs/setup/independent/high-availability.md index c78673783f..b75826675c 100644 --- a/docs/setup/independent/high-availability.md +++ b/docs/setup/independent/high-availability.md @@ -409,7 +409,7 @@ In an on-site environment there may not be a physical load balancer available. I As an example we outline a simple setup based on keepalived. Depending on environment and requirements people may prefer different solutions. The configuration shown here provides an _active/passive_ failover without load balancing. If required, load balancing can by added quite easily by setting up HAProxy, NGINX or similar on the master nodes (not covered in this guide). -1. Install keepalived, e.g. using your distribution's package manager. The configuration shown here works with version 1.3.5 and supposedly many others. Make sure to have it enabled (chkconfig, systemd, ...) so that it starts automatically when the respective node comes up. +1. Install keepalived, e.g. using your distribution's package manager. The configuration shown here works with version `1.3.5` but is expected to work with may other versions. Make sure to have it enabled (chkconfig, systemd, ...) so that it starts automatically when the respective node comes up. 2. Create the following configuration file _/etc/keepalived/keepalived.conf_ on all master nodes: