Uploaded image for project: 'OpenShift Specialist Platform Team'
  1. OpenShift Specialist Platform Team
  2. SPLAT-558

[aws][local-zones] research - deploy a new ingress-controller for ALB on Local Zones

    XMLWordPrintable

Details

    Description

      As a Customer I would like to deploy an AWS Application Load Balancer [NE-730 on a OpenShift cluster installed with support of Local Zones[SPLAT-557, so I can deploy user-workloads with sensitive latency close to the end users.

      This research complements the Day-0 to create a cluster on existing network with MachineSet for compute nodes on AWS Local Zones[2].

      DESCRIPTION

      Document the steps to create a new ingress-controller for ALB on Local Zones.

      Points of attention: We need to make sure the ALB will be fully supported in LZs which supports only one zone - multi-az was a requirement for ALB.

      Goal:

      • Document the steps to deploy a new ingress-controller and sample app using ALB on Local Zone
         

      ENGINEERING DOC

      [1] AWS Local Zone doc: https://aws.amazon.com/about-aws/global-infrastructure/localzones
      [2] Initial Research for Day-0: https://issues.redhat.com/browse/SPLAT-557 
      [3] ALB operator will be supported on 4.11: https://issues.redhat.com/browse/NE-730

      Attachments

        Issue Links

          is blocked by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SPLAT-557 [aws][local-zones] research - create a cluster with MachineSets in Local Zones(day-0)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Spike - Represents a research-related task. SPLAT-526 [aws][local-zones] research - extend compute nodes using subnets in Local Zones [day-2]

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Activity

            People

              rhn-support-mrbraga Marco Braga
              rhn-support-mrbraga Marco Braga
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day, 4 hours
                  1d 4h