On Tue, Dec 13, 2016 at 1:49 PM, Diego Castro
wrote:
> 2016-12-13 15:24 GMT-03:00 Jason DeTiberus :
>
>>
>>
>> On Tue, Dec 13, 2016 at 12:37 PM, Diego Castro <
>> diego.cas...@getupcloud.com> wrote:
>>
>>> Thanks John, it's very helpful.
>>> Looking over the playbook code, it's seems to replace a
2016-12-13 15:24 GMT-03:00 Jason DeTiberus :
>
>
> On Tue, Dec 13, 2016 at 12:37 PM, Diego Castro <
> diego.cas...@getupcloud.com> wrote:
>
>> Thanks John, it's very helpful.
>> Looking over the playbook code, it's seems to replace all certificates
>> and trigger node evacuation to update all pods
On Tue, Dec 13, 2016 at 12:37 PM, Diego Castro
wrote:
> Thanks John, it's very helpful.
> Looking over the playbook code, it's seems to replace all certificates and
> trigger node evacuation to update all pods CA, i definitely don't want that!
>
It should only do that when openshift_certificates
Thanks John, it's very helpful.
Looking over the playbook code, it's seems to replace all certificates and
trigger node evacuation to update all pods CA, i definitely don't want that!
- ETCD wont be a problem since i can replace the certs, migrate the datadir
and restart masters.
- Masters is a bi
Diego,
We’ve done a similar thing in our environment. I’m not sure if the
openshift-ansible guys have a better way, but this is what we did at that time.
We created a custom playbook to run through all the steps as necessary. And due
to the version of openshift-ansible we were running, we had t
Hello, i have to migrate my production HA masters/etcd servers to new boxes.
Steps Intended:
1) Create a new masters and etcd machines using byo/config playbook.
2) Stop the old masters and move etcd data directory to new etcd servers
3) Start the new masters
4) Run byo/openshift-cluster/redeploy
