diff options
| author | Monis Khan <mkhan@redhat.com> | 2017-10-06 11:06:50 -0400 |
|---|---|---|
| committer | Monis Khan <mkhan@redhat.com> | 2017-10-06 11:06:50 -0400 |
| commit | 2967d963d5185d7e77fe9b235886deaf64534a3c (patch) | |
| tree | 7b114bc578f72b31d2bbf2ab25868310c7481508 /roles | |
| parent | e7e82bede0f7ebac08a4290a3f088cca0ea3ab78 (diff) | |
| download | openshift-2967d963d5185d7e77fe9b235886deaf64534a3c.tar.gz openshift-2967d963d5185d7e77fe9b235886deaf64534a3c.tar.bz2 openshift-2967d963d5185d7e77fe9b235886deaf64534a3c.tar.xz openshift-2967d963d5185d7e77fe9b235886deaf64534a3c.zip | |
Switch to configmap leader election on 3.7 upgrade
This change sets the controllerConfig.election.lockName to
openshift-master-controllers on a 3.7 upgrade.
This is the default in a new 3.7 cluster. Important excerpt from
the docs inside the origin codebase (slightly modified):
There are two modes for lease operation - a legacy mode that
directly connects to etcd, and the preferred mode which coordinates
on a configmap or endpoint in the kube-system namespace. Because
legacy mode and the new mode do not coordinate on the same key, an
upgrade must stop all controllers before changing the configuration
and starting controllers with the new config.
Signed-off-by: Monis Khan <mkhan@redhat.com>
Diffstat (limited to 'roles')
0 files changed, 0 insertions, 0 deletions