diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2018-02-06 07:40:55 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-02-06 07:40:55 -0800 |
| commit | d512d781be3530997522fb38ba29ee7f33eae5c8 (patch) | |
| tree | 6156269eceba0af6d9b434737cbb63940dd9b0af /playbooks/openshift-node/private/certificates-backup.yml | |
| parent | f048e7dec959cd3a0d10d007d1afaa62864172e0 (diff) | |
| parent | 43138470ca05806403bd9ad1b99e0e581307b191 (diff) | |
| download | openshift-d512d781be3530997522fb38ba29ee7f33eae5c8.tar.gz openshift-d512d781be3530997522fb38ba29ee7f33eae5c8.tar.bz2 openshift-d512d781be3530997522fb38ba29ee7f33eae5c8.tar.xz openshift-d512d781be3530997522fb38ba29ee7f33eae5c8.zip | |
Merge pull request #7018 from mtnbikenc/refactor-cert-SAN
Automatic merge from submit-queue.
Move cert SAN update logic to openshift-etcd
Recent additions for checking certificate SAN validation were added to the upgrade playbooks and should be moved to the openshift-etcd playbooks to ensure this check is performed when the openshift-etcd upgrade playbook is run directly, vice only when running a full control plane upgrade. Additionally, the formerly included playbook for redeploying certificates called the main entry point playbook which caused the initialization playbooks to be called twice.
Diffstat (limited to 'playbooks/openshift-node/private/certificates-backup.yml')
0 files changed, 0 insertions, 0 deletions