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

Route tables should have a route for IPv6 ::/0 destination to EgressOnlyInternetGateway

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • None
    • Installer Sprint 274, Installer Sprint 275, Installer Sprint 276, Installer Sprint 277, Installer Sprint 278, Installer Sprint 279, Installer Sprint 280

      User Story:

      As a (user persona), if the cluster has IPv6 enabled, I'd to configure route tables for dual-stack private subnets to have a route that directs IPv6 internet traffic (::/0) to the EgressOnlyInternetGateway (eigw).

      Acceptance Criteria:

      Description of criteria:

      • A route needs adding to the managed route tables that directs IPv6 internet traffic to eigw.
      • If the eigw is recreated, CAPA should ensure the route is up to date.

       

      Destination Target
      ::/0 eigw-id

      (optional) Out of Scope:

      Detail about what is specifically not being delivered in the story

      Engineering Details:

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

              rh-ee-thvo Thuan Vo
              rh-ee-thvo Thuan Vo
              None
              None
              Yunfei Jiang Yunfei Jiang
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: