-
Notifications
You must be signed in to change notification settings - Fork 167
Change Attach Limit to Hyperdisk Balanced Only #2126
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
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sunnylovestiramisu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold |
/test pull-gcp-compute-persistent-disk-csi-driver-e2e |
@sunnylovestiramisu: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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-sigs/prow repository. I understand the commands that are listed here. |
Hi, I believe this fix may introduce side effects since each machine family has different limits. The current approach would only work properly for the N4 family. For better clarity and correctness, we should use different limit maps based on the machine type, with each map containing the specific limits for that family. I'll submit a separate PR that addresses this concern. |
As mentioned, I created this alternative PR: |
/close In favor of #2127 |
@sunnylovestiramisu: Closed this PR. 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-sigs/prow repository. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: