Loading...

XML

Word

Printable

Type: Story
Resolution: Done
Priority: Blocker
Fix Version/s: openshift-4.16
Affects Version/s: None
Component/s: None
Labels:
- aws
- splatteam

Work Type:
Strategic Product Work
Story Points:
3
Epic Link:
AWS CAPI Infrastructure (no mgmt cluster)
Feature Link:
OCPSTRAT-1007 - Remove Terraform from the AWS IPI installer

Original story points:
3
Sprint:
OpenShift SPLAT - Sprint 252, OpenShift SPLAT - Sprint 253

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Use cases to ensure:

When installconfig.controlPlane.platform.aws.zones is specified, control plane nodes are correctly placed in the zones.
When installconfig.controlPlane.platform.aws.zones isn't specified, the control plane nodes are correctly balanced in the zones available in the region, preventing single-zone when possible.

clones

CORS-2885 control plane nodes and subnets are correctly distributed among zones

Closed

is cloned by

CORS-3479 control plane nodes and subnets are correctly distributed among zones with no config

Closed

links to

openshift/installer#8156: CORS-2895: aws/capi: setting zones to when creating cluster

openshift/installer#8347: CORS-2895: capa/machines: fix zone placement for control planes

Assignee:: Marco Braga

Reporter:: Patrick Dillon

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2023/10/19 3:19 PM

Updated:: 2024/09/04 8:10 PM

Resolved:: 2024/05/14 1:43 PM