-
Bug
-
Resolution: Done
-
Normal
-
None
-
CNV v4.16.0
-
None
-
Quality / Stability / Reliability
-
3
-
False
-
-
False
-
None
-
Green
-
-
Moderate
-
None
Description of problem:
The “type” parameter in the following document shows the old value “cnv-bridge”. It would be more appropriate to use “bridge” now.
https://docs.openshift.com/container-platform/4.16/virt/vm_networking/virt-connecting-vm-to-linux-bridge.html#virt-creating-linux-bridge-nad-cli_virt-connecting-vm-to-linux-bridge
apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
name: bridge-network
annotations:
k8s.v1.cni.cncf.io/resourceName: bridge.network.kubevirt.io/bridge-interface
spec:
config: '{
"cniVersion": "0.3.1",
"name": "bridge-network",
"type": "cnv-bridge",
"bridge": "bridge-interface",
"macspoofchk": false,
"vlan": 100,
"disableContainerInterface": "true",
"preserveDefaultVlan": false
}'
This parameter has been corrected below.
UI should use type "bridge" instead of "cnv-bridge"
https://issues.redhat.com/browse/OCPBUGS-34011
Only 4.14 doc fix tickets were drafted, but 4.15 and 4.16 docs do not seem to have been fixed.
CNV-38825
Network documentation should use type "bridge" instead of "cnv-bridge"
https://issues.redhat.com/browse/CNV-38825
Actual results:
Use cnv-bridge "type": "cnv-bridge",
Expected results:
Use bridge "type": "bridge",
- impacts account
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- links to
