Uploaded image for project: 'Network Hardware Enablement'
  1. Network Hardware Enablement
  2. NHE-334

BF doesn't connect to tenant cluster due to missing DNS entry

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • DPU
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      possibly the fix involves coredns

       

      Same issue for DPU network operator pod.

      Workaround:

      • run dpu network operator as host network pod
      • add entry to /etc/hosts on all nodes

          1.
          		 Fix automation to set DNS properly Sub-task Closed Undefined Balazs Nemeth
          2.
          		 Write up docs on how user should set DNS Sub-task Closed Undefined Balazs Nemeth

              bnemeth@redhat.com Balazs Nemeth
              bnemeth@redhat.com Balazs Nemeth
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: