summaryrefslogtreecommitdiffstats
path: root/playbooks/common/openshift-cluster/upgrades/v3_7/master_config_upgrade.yml
Commit message (Collapse)AuthorAgeFilesLines
* Combine master upgrade play with roleMichael Gugino2017-11-091-20/+0
| | | | | | | | | Currently, there are plays importing tasks directly from openshift_master role. This has caused numerous bugs and code duplicaiton in the past. This commit combines the upgrade into openshift_master role utilizing include_role syntax.
* Merge pull request #5749 from abutcher/servinginfo-client-ca-upgradeOpenShift Merge Robot2017-10-201-0/+5
|\ | | | | | | | | | | | | Automatic merge from submit-queue. Set servingInfo.clientCA to ca.crt during upgrade. https://bugzilla.redhat.com/show_bug.cgi?id=1501795
| * Set servingInfo.clientCA to ca.crt during upgrade.Andrew Butcher2017-10-171-0/+5
| |
* | Remove unneeded master config updates during upgradesMichael Gugino2017-10-171-16/+0
|/ | | | | | | | | | | | | | | | | Currently, upgrade_control_plane.yml will add any missing sections to the openshift master's config. These additions are only needed once. Users who perform multiple upgrades to their clusters over time do not need to have these variables re-inserted. Currently, re-inserting these variables can cause unwanted local changes. This commit ensures that the variables are only inserted into openshift master's config once. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1486054
* Ensure controllerConfig.serviceServingCert is correctly set during upgrade.Andrew Butcher2017-10-131-0/+10
|
* Switch to configmap leader election on 3.7 upgradeMonis Khan2017-10-061-0/+5
| | | | | | | | | | | | | | | | | 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>
* Add v3_7 upgradesScott Dodson2017-08-081-0/+16