From e8fa5cdd331d2fe3936dcd3f3724f1724047852d Mon Sep 17 00:00:00 2001 From: Sebastiaan van Steenis Date: Thu, 4 Apr 2019 14:26:20 +0200 Subject: [PATCH] Add Rancher leader election to troubleshooting --- .../v2.x/en/troubleshooting/rancherha/_index.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/content/rancher/v2.x/en/troubleshooting/rancherha/_index.md b/content/rancher/v2.x/en/troubleshooting/rancherha/_index.md index 9ef9d9e0d99..5a90616e985 100644 --- a/content/rancher/v2.x/en/troubleshooting/rancherha/_index.md +++ b/content/rancher/v2.x/en/troubleshooting/rancherha/_index.md @@ -68,3 +68,13 @@ When accessing your configured Rancher FQDN does not show you the UI, check the ``` kubectl -n ingress-nginx logs -l app=ingress-nginx ``` + +### Leader election + +The leader is determined by a leader election process. After the leader has been determined, the leader (`holderIdentity`) is saved in the `cattle-controllers` ConfigMap (in this example, `rancher-7dbd7875f7-qbj5k`). + +``` +kubectl -n kube-system get configmap cattle-controllers -o jsonpath='{.metadata.annotations.control-plane\.alpha\.kubernetes\.io/leader}' +{"holderIdentity":"rancher-7dbd7875f7-qbj5k","leaseDurationSeconds":45,"acquireTime":"2019-04-04T11:53:12Z","renewTime":"2019-04-04T12:24:08Z","leaderTransitions":0} +``` +