Yes, we have tested clusterNetworkCIDR changes in a running cluster, but
there are still some related known issues as below. If you have
important data in the cluster, you'd better backup them first.
https://bugzilla.redhat.com/show_bug.cgi?id=1311849
https://bugzilla.redhat.com/show_bug.cgi?id=1470612
Thanks.
On 07/25/2017 01:53 PM, Łukasz Strzelec wrote:
Hello :)
True , as I mentioned, I had read the documentation. I was about, does
anybody try to do this on already running cluster? I want to spare
our customers downtimes and migration between clusters.
Best regards
2017-07-25 5:28 GMT+02:00 bmeng <[email protected]
<mailto:[email protected]>>:
Yeah, it is possible but has some limitations.
Please refer to:
https://docs.openshift.com/container-platform/3.5/install_config/configuring_sdn.html#configuring-the-pod-network-on-masters
<https://docs.openshift.com/container-platform/3.5/install_config/configuring_sdn.html#configuring-the-pod-network-on-masters>
*** The serviceNetworkCIDR and hostSubnetLength values cannot be
changed after the cluster is first created, and clusterNetworkCIDR
can only be changed to be a larger network that still contains the
original network.
On 07/25/2017 01:26 AM, Łukasz Strzelec wrote:
Hello :)
Is there a chance to change |*clusterNetworkCIDR, *after
installation*?
*|
I read documentation , but maybe someone did such a things ?
Best regards
--
Ł.S.
_______________________________________________
users mailing list
[email protected]
<mailto:[email protected]>
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
<http://lists.openshift.redhat.com/openshiftmm/listinfo/users>
--
Ł.S.
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
