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

[enterprise-4.15] Issue in file virt/vm_networking/virt-accessing-vm-secondary-network-fqdn.adoc

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • None
    • 4.15
    • Documentation / Virtualization
    • None
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      In this section of the document [1], the order of steps is not correct

[1] https://docs.openshift.com/container-platform/4.15/virt/vm_networking/virt-accessing-vm-secondary-network-fqdn.html#virt-configuring-secondary-dns-server_virt-accessing-vm-secondary-network-fqdn

      Additional info:

      The correct order of Configuring a DNS server for secondary networks should be:

1- Enable "deployKubeSecondaryDNS" feature
2- Create a load balancer service to expose the DNS server outside the cluster
3- Edit HyperConverged instance and configure the kubeSecondaryDNSNameServerIP with the external IP from the previous step

       

      The steps provided here are to show the correct order only and not the actual Text to be used in the document's section.

            Unassigned Unassigned
            rhn-support-aelganzo Amr Elganzory
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: