Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-29669

ovn-k multi-homing: confusing explanation for the `subnets` attribute

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 1
    • Important
    • No
    • None
    • None
    • None
    • OSDOCS Sprint 253
    • 1
    • In Progress
    • Release Note Not Required
    • None
    • None
    • None
    • None
    • None

      Description of problem:

          The `subnets` attribute explanation, in the network plugin JSON configuration table - [0] - is confusing; it starts with "The subnet to use for the network across the cluster. When specifying layer2 for the topology, only include the CIDR for the node. For example, 10.100.200.0/24." 
      
      I think the second sentence is very confusing, and could be omitted.
      
      Thus - IMO - it should instead read: "The subnet to use for the network across the cluster."
      
      The rest of the attribute's description is OK.
      
      [0] - https://docs.openshift.com/container-platform/4.14/networking/multiple_networks/configuring-additional-network.html#configuration-ovnk-network-plugin-json-object_configuring-additional-network

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

          4.14.Z

      How reproducible:

          Always

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

          The subnets attribute is poorly explained - especially the part about "only include the CIDR for the node". 

      Expected results:

          A clear and concise explanation of the subnets attribute.

      Additional info:

          

              rhn-support-stevsmit Steven Smith
              mduarted@redhat.com Miguel Duarte de Mora Barroso
              None
              None
              Zhanqi Zhao Zhanqi Zhao
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: