Clarifying that NETWORK_ISOLATION is set to true by default

Signed-off-by: Jiri Podivin <[email protected]>

Author: jpodivin

README.md

@@ -103,8 +103,7 @@ REDHAT_OPERATORS=true make openstack
 ```bash
 make openstack_init
 ```
-
-**Note** this will also run the openstack_prep target, which if NETWORK_ISOLATION == true will install nmstate and metallb operator, configure the secondary interface of the crc VM via nncp, creates the network-attachment-definitions for datacentre, internalapi, storage and tenant network. Also the metallb l2advertisement and the ipaddresspools get created.
+**Note** this will also run the openstack_prep target, which will install nmstate and metallb operator, configure the secondary interface of the crc VM via nncp, creates the network-attachment-definitions for datacentre, internalapi, storage and tenant network, unless `NETWORK_ISOLATION == false`. Also the metallb l2advertisement and the ipaddresspools get created.
 
 The following NADs with ip ranges get configured:
 ```
@@ -130,6 +129,7 @@ HOSTNETWORK=false NETWORKS_ANNOTATION=\'[\{\"name\":\"storage\",\"namespace\":\"
 * deploy the ctlplane
 
 If `NETWORK_ISOLATION == true`, `config/samples/core_v1beta1_openstackcontrolplane_network_isolation.yaml` will be used, if `false` then `config/samples/core_v1beta1_openstackcontrolplane.yaml`.
+`NETWORK_ISOLATION` is set to true by default.
 
 ```bash
 make openstack_deploy