-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17.z
Description of problem:
Despite passing in '--attach-default-network false', the nodepool still has attachDefaultNetwork: true
hcp create cluster kubevirt --name ocp-lab-int-6 --base-domain paas.com --cores 6 --memory 64Gi --additional-network "name:default/ppcore-547" --attach-default-network false --cluster-cidr 100.64.0.0/20 --service-cidr 100.64.16.0/20 --network-type OVNKubernetes --node-pool-replicas 3 --ssh-key ~/deploy --pull-secret pull-secret.txt --release-image quay.io/openshift-release-dev/ocp-release:4.16.18-x86_64
platform:
kubevirt:
additionalNetworks:
- name: default/ppcore-547
attachDefaultNetwork: true
Version-Release number of selected component (if applicable):
Client Version: openshift/hypershift: b9e977da802d07591cd9fb8ad91ba24116f4a3a8. Latest supported OCP: 4.17.0
Server Version: b9e977da802d07591cd9fb8ad91ba24116f4a3a8
Server Supports OCP Versions: 4.17, 4.16, 4.15, 4.14
How reproducible:
Steps to Reproduce:
1. hcp install as per the above
2.
3.
Actual results:
The default network is attached
Expected results:
No default network
Additional info:
