Closed stmcginnis closed 2 months ago
Welcome @stmcginnis!
It looks like this is your first PR to kubernetes-csi/csi-driver-iscsi 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.
You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.
You can also check if kubernetes-csi/csi-driver-iscsi has its own contribution guidelines.
You may want to refer to our testing guide if you run into trouble with your tests not passing.
If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to Kubernetes. :smiley:
Hi @stmcginnis. Thanks for your PR.
I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: stmcginnis Once this PR has been reviewed and has the lgtm label, please assign msau42 for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
When closing these can you please indicate why and what needs to be done as a next step?
pls make the changes in csi-release-tools first, and then vendor the change into this repo
Any help getting the CI issues fixed in the release-tools repo to help get that change through would be appreciated. ;)
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
The
--kube-root
flag has been deprecated in kind for some time and will be removed. The current equivalent functionality is to pass the path to the kubernetes source as the first non-flag argument tobuild node-image
.This updates the prow script to use the newer preferred method in preparation for kind dropping the flag.
Which issue(s) this PR fixes:
Related: https://github.com/kubernetes-sigs/kind/issues/3717
Special notes for your reviewer:
Does this PR introduce a user-facing change?: