You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ci-operator/templates/openshift/installer/cluster-launch-installer-*: Random AWS regions for IPI
I'm leaving the UPI templates and such alone for now, because they
mention regions in more places and I don't care as much about them ;).
The approach mirrors what we did for Azure with 4d08a9d
(ci-operator/templates/openshift/installer/cluster-launch-installer-*:
Random Azure regions, 2019-09-18, #5081). This should reduce resource
contention (both for limits and for API throttling) in CI. We could
theoretically raise our Boskos caps as well, but I'm leaving that off
for now because we're getting hammered by AMI-copy issues [1].
I've also added ZONE_* variables in case we need to dodge broken zones
like we have in the past with e8921c3
(ci-operator/templates/openshift: Get e2e-aws out of us-east-1b,
2019-03-22, #3204). I have nothing against the other us-east-1 zones
at the moment, the current ZONE_* overrides there are just to
demonstrate the idea in case folks need to pivot later. Without
explicit ZONE_* choices, we'll fall back to using zones a and b within
the chosen region.
The DevProductivity Platform (DPP) folks bumped our quotas in the new
regions back in 2019-11 [2]. We should be good for up to 25% of our
current us-east-1 capacity in those regions. Increases beyond that,
or sharding into additional regions, will require additional DPP <->
AWS work to get limits raised.
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1752370#c3
[2]: https://issues.redhat.com/browse/DPP-3108
0 commit comments