From f3888e24556397ea9b018cc25836c41ac2b007ef Mon Sep 17 00:00:00 2001 From: Christophe Fergeau Date: Wed, 20 Jan 2021 15:41:05 +0100 Subject: [PATCH] Change clusterNetwork/serviceNetwork CIDR once more This was initially changed because it was causing issues when running crc in an OpenShift cluster. However the new one causes collisions in a different environment. Let's try a 3rd different value and see if we are lucky this time :) I picked: - an odd number - bigger than 200 in the hope that sysadmins are less likely to see this as a good value to use for internal networks. This commit also picks smaller network ranges for the serviceNetwork and clusterNetwork, as snc is single node, a /22 for clusterNetwork should be plenty enough. A /23 can't be used because of https://github.com/openshift/sdn/issues/250 This also changes the service network to use a /23 right after the network used for clusterNetwork. This means crc uses addresses from 10.217.0.0 to 10.217.5.255. --- install-config.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/install-config.yaml b/install-config.yaml index 140cc2de..1c536d57 100644 --- a/install-config.yaml +++ b/install-config.yaml @@ -19,13 +19,13 @@ metadata: name: crc networking: clusterNetwork: - - cidr: 10.116.0.0/14 + - cidr: 10.217.0.0/22 hostPrefix: 23 machineNetwork: - cidr: 192.168.126.0/24 networkType: OpenShiftSDN serviceNetwork: - - 172.25.0.0/16 + - 10.217.4.0/23 platform: libvirt: URI: qemu+tcp://192.168.122.1/system