Assuming a production cluster, ... I wouldn't want to take any
responsibility not knowing your setup.
I've seen scaleup and upgrade playbooks fail, in 3.7, 3.9, 3.10, 3.11, ...
especially when crio and/or proxies are involved.
Sure, the upgrade playbooks should leave your cluster in a consistent
Hi, all
I'm new to the list. Perhaps, smb already asked this question:
When I start a cluster using *oc cluster up* command, Openshift generates a
self-signed certificate. Is it possible to give it a real certificate?
Thanks in advance.
Regards,
Pavel Maslov, MS
Hi, I re-send the email to the mailing list, I sent it directly to Samuel
instead
What I meant it is to refresh the inventory,
I think I finally managed to refresh it running the following playbook
- hosts: masters
gather_facts: no
tasks:
- name: Refresh inventory to ensure new instaces
Hello Samuel,
Assuming a production cluster; is running the upgrade_cluster sufficient?
On 02/25/2019 11:40 AM, Samuel Martín Moro wrote:
Hi,
Can you explain what do you mean by re-configuring the inventory in
all your nodes?
Editing your ansible inventory doesn't require to apply any
Hi,
Can you explain what do you mean by re-configuring the inventory in all
your nodes?
Editing your ansible inventory doesn't require to apply any playbook.
Although having done so, you should make sure those modifications won't
interfere with whatever scapeup or upgrade playbook you'll
Hi,
I am running okd 3.11 and I would like to know how to re-configure the
inventory in all my nodes, is there any ansible-playbook to run?
Cheers,
Iago.
___
users mailing list
users@lists.openshift.redhat.com
