-
Notifications
You must be signed in to change notification settings - Fork 803
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
Allow volume attach limit overwrite via command line parameter #522
Allow volume attach limit overwrite via command line parameter #522
Conversation
Hi @rfranzke. 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. 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 @leakingtapan |
cc @gnufied |
Pull Request Test Coverage Report for Build 1125
💛 - Coveralls |
59f1ab9
to
426c3e5
Compare
/ok-to-test |
@gnufied: Cannot trigger testing until a trusted user reviews the PR and leaves an 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good, just a minor comment.
/ok-to-test |
@leakingtapan @wongma7 It would be helpful if you could also take a quick look. It seems like a reasonable change, to not break the user experience with CSI migration on AWS/EKS. Basically the
|
Giving @leakingtapan a chance to chime in as he had some objections to this but I agree it's necessary to make the limit configurable somehow and a flag seems the best way. |
@leakingtapan Do you have some time to check the PR? Any thoughts on it? |
Hm, what's the general review process now? As @leakingtapan seems to be busy/inactive, can another owner/approver help to progress with this PR? @bertinatto @jsafrane @gnufied @wongma7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly looks good to me.
426c3e5
to
0b554b6
Compare
/retest |
@gnufied I've dropped all unrelated changes. |
Btw, any pointers on how to get the e2e tests fixed? They fail unrelatedly, see https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_aws-ebs-csi-driver/522/pull-aws-ebs-csi-driver-e2e-multi-az/1275303611722633217/build-log.txt.
|
Looks good to me but we might want to wait for @leakingtapan feedback too. /lgtm |
@gnufied: changing LGTM is restricted to collaborators 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking the effort to improve current situation. Agree that's the best option we have now. Left one comment
b9b1662
to
56e2559
Compare
56e2559
to
2d9fe32
Compare
/retest |
2 similar comments
/retest |
/retest |
/hold cancel |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gnufied, leakingtapan, rfranzke 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 |
this is configurable in the helm chart here |
Is this a bug fix or adding new feature?
/kind feature
What is this PR about? / Why do we need it?
This PR is a part of #347 and proceeds with the way suggested in #347 (comment): In order to allow existing clusters that are leveraging/relying on the
KUBE_MAX_PD_VOLS
feature for in-tree provisioners in Kubernetes (https://kubernetes.io/docs/concepts/storage/storage-limits/#custom-limits) to migrate to CSI, the EBS CSI driver is supporting the--volume-attach-limit-overwrite
flag now until a more sophisticated solution can be implemented.PS: I was adding a few missing doc strings along the way and reduced package/function name stuttering according to the official Go suggestions. Hope that's fine.