-
Feature
-
Resolution: Unresolved
-
Critical
-
None
-
False
-
-
False
-
33% To Do, 17% In Progress, 50% Done
-
S
-
0
-
0
-
-
-
I am marking this Readiness Candidate because awarness of the upcomming AWS changes is good; as well as knowing how / what can be done in this space would be good as customers will have questions.
-
-
-
Feature Overview (aka. Goal Summary)
The default OpenShift installation on AWS uses multiple IPv4 public IPs which Amazon will start charging for starting in February 2024. As a result, there is a requirement to find an alternative path for OpenShift to reduce the overall cost of a public cluster while this is deployed on AWS public cloud.
Goals (aka. expected user outcomes)
Provide an alternative path to reduce the new costs associated with public IPv4 addresses when deploying OpenShift on AWS public cloud.
Requirements (aka. Acceptance Criteria):
There is a new path for "external" OpenShift deployments on AWS public cloud where the new costs associated with public IPv4 addresses have a minimum impact on the total cost of the required infrastructure on AWS.
Background
Ongoing discussions on this topic are happening in Slack in the #wg-aws-ipv4-cost-mitigation private channel
Documentation Considerations
Usual documentation will be required in case there are any new user-facing options available as a result of this feature.
- relates to
-
NE-1274 AWS BYO Static EIP Support for Default Ingress/Router w/NLB
-
- In Progress
-
-
-
- Refinement
-
- links to
