Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Ability to specify Availability Zones from the VPCSpec object #4333

Open
Tracked by #3853
synthe102 opened this issue Jun 12, 2023 · 11 comments · May be fixed by #4950
Open
Tracked by #3853

Ability to specify Availability Zones from the VPCSpec object #4333

synthe102 opened this issue Jun 12, 2023 · 11 comments · May be fixed by #4950
Assignees
@Skarlso
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@synthe102
Copy link
Contributor

/kind feature

Describe the solution you'd like

Currently the AZ selection can be done using availabilityZoneUsageLimit and availabilityZoneSelection. 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:

  • Cluster-api-provider-aws version: 2.1.4
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 12, 2023
@synthe102 synthe102 mentioned this issue Jun 12, 2023
Open
2 tasks
@Ankitasw
Copy link
Member

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 13, 2023
@synthe102
Copy link
Contributor Author

/milestone v2.3.0

@k8s-ci-robot
Copy link
Contributor

@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:

/milestone v2.3.0

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.

@richardcase
Copy link
Member

/milestone v2.3.0
/help
/priority important-soon

@k8s-ci-robot
Copy link
Contributor

@richardcase:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

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
by commenting with the /remove-help command.

In response to this:

/milestone v2.3.0
/help
/priority important-soon

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.

@k8s-ci-robot k8s-ci-robot added this to the v2.3.0 milestone Jul 10, 2023
@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. and removed needs-priority labels Jul 10, 2023
@Skarlso
Copy link
Contributor

Skarlso commented Oct 2, 2023

/assign

@Skarlso
Copy link
Contributor

Skarlso commented Oct 4, 2023

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 ).

@Skarlso
Copy link
Contributor

Skarlso commented Oct 4, 2023

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 Skarlso mentioned this issue Oct 5, 2023
Closed
4 tasks
@synthe102
Copy link
Contributor Author

@Skarlso it makes sense for me to ignore those and make the user assume the consequences

@k8s-triage-robot
Copy link

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged.
Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

  • Confirm that this issue is still relevant with /triage accepted (org members only)
  • Deprioritize it with /priority important-longterm or /priority backlog
  • Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. and removed triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Jan 19, 2024
@richardcase
Copy link
Member

/milestone v2.4.0

@k8s-ci-robot k8s-ci-robot modified the milestones: v2.3.0, v2.4.0 Jan 19, 2024
@richardcase richardcase removed this from the v2.4.0 milestone Jan 23, 2024
@synthe102 synthe102 linked a pull request Apr 23, 2024 that will close this issue
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Skarlso Skarlso

Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
No milestone
6 participants
@Skarlso @richardcase @k8s-ci-robot @k8s-triage-robot @synthe102 @Ankitasw