🐛 Fix Provisioning to Unavailable AZs#1479
Conversation
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
Hi @spjmurray. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
Could you please fix the commit message and check the linter error ( |
mdbooth
left a comment
There was a problem hiding this comment.
Looks good in principal. Just need to update the unit tests for the webhook change and to avoid creating dead code in availabilityzones.go.
CAPO uses any ZA it finds, rather than checking whether the ZA is actually available, meaning you can get into a state where it's impossible to provision a cluster. This allows clients to filter based on AZ availability before scheduling.
|
/approve Thanks! I'll leave lgtm to another reviewer. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mdbooth, spjmurray The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@spjmurray If you cancel the hold this will merge. |
|
/cherry-pick release-0.7 |
|
@mdbooth: once the present PR merges, I will cherry-pick it on top of release-0.7 in a new PR and assign it to you. DetailsIn 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. |
|
/hold cancel |
|
@mdbooth: new pull request created: #1488 DetailsIn 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. |
CAPO uses any ZA it finds, rather than checking whether the ZA is actually available, meaning you can get into a state where it's impossible to provision a cluster. This allows clients to filter based on AZ availability before scheduling.
Fixes #1477
What this PR does / why we need it:
Discussion in #1477
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
TODOs:
/hold