-
Notifications
You must be signed in to change notification settings - Fork 541
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to specify Availability Zones from the VPCSpec
object
#4333
Comments
/triage accepted |
/milestone v2.3.0 |
@synthe102: You must be a member of the kubernetes-sigs/cluster-api-provider-aws-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Cluster API Provider AWS Maintainers and have them propose you as an additional delegate for this responsibility. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/milestone v2.3.0 |
@richardcase: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign |
Since availability zones are per region, defining a list of availability zones might not work in some of the regions. Question... @synthe102 Would you expect the two settings of confinement ( AvailabilityZoneUsageLimit, AvailabilityZoneSelection ) to still work, or for them to be completely ignored if the list if defined ( thereby accepting the consequences that things might start to fail ). |
I'm going to assume for now that ignoring the other two if this one is set, is okay and the user accepts the consequences. |
@Skarlso it makes sense for me to ignore those and make the user assume the consequences |
This issue is labeled with You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
/milestone v2.4.0 |
/kind feature
Describe the solution you'd like
Currently the AZ selection can be done using
availabilityZoneUsageLimit
andavailabilityZoneSelection
. However, there is no direct way to provide a list of availability zones to use.I'd like a field that takes a list of availability zone names (or zone IDs) and create the VPC and subnets only in those availability zones.
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: