diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2017-10-07 08:16:43 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-10-07 08:16:43 -0700 |
| commit | cb1d90e36131f05035adc7ec5a0d280fd2126fcc (patch) | |
| tree | 8232853798fe5d9f8503ecbd0ab2b6375698ac5b /roles/openshift_node_facts | |
| parent | 88191454aff1542c9b094b2dda06445d77217022 (diff) | |
| parent | 2967d963d5185d7e77fe9b235886deaf64534a3c (diff) | |
| download | openshift-cb1d90e36131f05035adc7ec5a0d280fd2126fcc.tar.gz openshift-cb1d90e36131f05035adc7ec5a0d280fd2126fcc.tar.bz2 openshift-cb1d90e36131f05035adc7ec5a0d280fd2126fcc.tar.xz openshift-cb1d90e36131f05035adc7ec5a0d280fd2126fcc.zip | |
Merge pull request #5684 from enj/enj/i/configmap_lock
Automatic merge from submit-queue.
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>
/assign @smarterclayton @jupierce
/kind bug
Diffstat (limited to 'roles/openshift_node_facts')
0 files changed, 0 insertions, 0 deletions