-
Spike
-
Resolution: Obsolete
-
Critical
-
None
-
None
-
False
-
None
-
False
-
-
Goal:
- Answer the open questions to expand or make the Epic (
SPLAT-1149) invalid for supporting NAT Gateways in AWS Local Zones. - Open questions:
- options to support it in hybrid mode (does AWS provides an API to show supported features [NAT GW] in the Local Zone, or just a landing page?)
- if is API doesn't exists, will we need to keep a static list in installer with supported zones, and provide one field to force include it?
- Will the logic became complex (terraform mapping, etc)?
- Will we need to expand the storage options too (from announcement - maybe in another Epic) ?
ENGINEERING REFERENCES:
- AWS Announcement: https://aws.amazon.com/about-aws/whats-new/2023/07/aws-local-zone-phoenix-arizona/
- AWS Announcement blog: https://aws.amazon.com/blogs/aws/new-aws-local-zone-in-phoenix-arizona-more-instance-types-more-ebs-storage-classes-and-more-services/
- Slack thread: https://redhat-internal.slack.com/archives/C011MLLLY4W/p1690663608616059