Uploaded image for project: 'OpenShift Installer'
  1. OpenShift Installer
  2. CORS-2317

Update Ingress LB IP and DNSManagementPolicy within the Ingress Controller

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Undefined
    • None
    • None
    • None
    • None

    Description

      User Story:

      As a (user persona), I want to be able to:

      • Capability 1
      • Capability 2
      • Capability 3

      so that I can achieve

      • Outcome 1
      • Outcome 2
      • Outcome 3

      Acceptance Criteria:

      Description of criteria:

      • Upstream documentation
      • Point 1
      • Point 2
      • Point 3

      (optional) Out of Scope:

      Detail about what is specifically not being delivered in the story

      Engineering Details:

      • https://github.com/openshift/api/pull/1685 introduced updates that allows the  LB IPs to be added to GCPPlatformStatus along with the state of DNS for the cluster.
      • Update cluster-ingress-operator to add the Ingress LB IPs when DNSType is `ClusterHosted`
      • In this state, Within https://github.com/openshift/api/blob/master/operatoringress/v1/types.go set the DNSManagementPolicy to Unmanaged within the DNSRecordSpec when the DNS manifest has customer Managed DNS enabled. 
      • With the DNSManagementPolicy set to Unmanaged, the IngressController should not try to configure DNS records.

      This requires/does not require a design proposal.
      This requires/does not require a feature gate.

       

      Attachments

        Activity

          People

            sdasu@redhat.com Sandhya Dasu
            sdasu@redhat.com Sandhya Dasu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: