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

Ensure users are told to avoid creating a secondary OVN-K network named `default`

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • 4.17
    • 4.13.z, 4.14.z, 4.15.z, 4.17.z, 4.16.z
    • Documentation / SDN
    • Critical
    • No
    • 3
    • OSDOCS Sprint 255, OSDOCS Sprint 256
    • 2
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      The network named `default` is the default cluster network - in fact, that's literally the criteria to identify the default cluster network in the system.
      
      For that matter, we should call out to our users to not create a network with that name, since it risks confusing OVN-Kubernetes.

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

       

      How reproducible:

      Always

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

      We should ensure ours users know they should not be naming their networks `default`.

      Expected results:

      A callout indicating the network name can never be `default`.

      Additional info:

      I think the right way is to provide a note/callout in this section: https://docs.openshift.com/container-platform/4.15/networking/multiple_networks/configuring-additional-network.html#configuration-ovnk-additional-networks_configuring-additional-network

            dfitzmau@redhat.com Darragh Fitzmaurice
            mduarted@redhat.com Miguel Duarte de Mora Barroso
            Zhanqi Zhao Zhanqi Zhao
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: