Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-66285

Docs lead people to use bridge CNI instead of localnet

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • CNV Documentation
    • None
    • Quality / Stability / Reliability
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None

      Description of problem:

      We are positioning OVN localnet as the recommended way of connecting VMs to VLANs. Even though there are cases where bridge CNI may perform better or have features that are not yet available in localnet. The note "A Linux bridge network attachment definition is the most efficient method for connecting a virtual machine to a VLAN." makes it sound like a generally better CNI which it is not.
      
      I'd like to remove this note from the 2 places where we state this.
      
      We don't need to add anything new, the network overview already states: "The localnet topology is the recommended way of exposing VMs to the underlying physical network, with or without VLAN encapsulation."

      Version-Release number of selected component (if applicable):

      4.19

      How reproducible:

      Docs

      Steps to Reproduce:

      1. Go to https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/virtualization/networking
      2. Search for "most efficient method "

      Actual results:

      Two places where we state that

      Expected results:

      The note is not there

      Additional info:

       

              sjhala@redhat.com Shikha Jhala
              phoracek@redhat.com Petr Horacek
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: