-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Reduce GCE PD Attach Limits by 1 because Node Boot Disk counts as 1 attached disk #80923
Conversation
/kind bug |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: davidz627 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 |
/lgtm |
looks good to me too! we already do this for AWS and on AWS in fact we leave more than one disk to account for boot disk and may be disk for docker setup. many installations that use overlay2 prefer their own disk for docker |
/hold cancel |
/retest Review the full test history for this PR. Silence the bot with an |
1 similar comment
/retest Review the full test history for this PR. Silence the bot with an |
…923-upstream-release-1.14 Automated cherry pick of #80923: Reduce GCE PD Attach Limits by 1 because Node Boot Disk
…923-upstream-release-1.15 Automated cherry pick of #80923: Reduce GCE PD Attach Limits by 1 because Node Boot Disk
…923-upstream-release-1.13 Automated cherry pick of #80923: Reduce GCE PD Attach Limits by 1 because Node Boot Disk
PD CSI Driver xref: kubernetes-sigs/gcp-compute-persistent-disk-csi-driver#361
Fixes: kubernetes-sigs/gcp-compute-persistent-disk-csi-driver#360
Original issue uncovered by: #80247
Should probably be cherry-picked appropriately since this is a bug that will manifest since attach limits introduced
/assign @msau42 @jsafrane
/kind bug