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

GWAPI doesn't create DNS records for Gateways that are manually linked

XMLWordPrintable

    • Moderate
    • No
    • Sprint 239, Sprint 240, Sprint 241, Sprint 242, Sprint 243, Sprint 244, Sprint 245, Sprint 246, Sprint 247, Sprint 248, Sprint 249
    • 11
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      For our release of Gateway API support in the cluster-ingress-operator (Enhanced Dev Preview), it reconciles DNS Records for Gateways that use Auto Deployments, but it ignores Gateways that use Manual Deployment linking.

This means the DNS solution is incomplete and users have to manually configure DNS for Gateways with manual deployment/service linking (aka setting spec.addresses on the Gateway).

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

      4.13

      How reproducible:

      100%

      Steps to Reproduce:

      1. Turn on the Feature Gate for GWAPI (I can link our how-to doc here when we write it...)
2. Create Gateway that manually likes to the default istio-ingressgateway
3. No DNS Record created

      Actual results:

      No DNS Record created

      Expected results:

      DNS Record created for hostnames in your Gateway that is manually linked

      Additional info:

       

              mmasters1@redhat.com Miciah Masters
              gspence@redhat.com Grant Spence
              Hongan Li Hongan Li
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: