-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Be more clear on the expected format of --wait option #3419
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
|
Hi @radeksm. 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. |
neolit123
left a comment
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
|
/ok-to-test |
|
/test pull-kind-e2e-kubernetes-1-24 |
|
/lgtm |
|
FWIW, this problem exists in kubectl as well, e.g. This change seems fine, but I prefer to align with |
@BenTheElder I will create new pull req to adjust in for kubectl so we can make it more clear and consistent. Actually the same kind of inconsistency exists in kubectl on blow three subcommands too: |
|
/test pull-kind-e2e-kubernetes-1-24 |
b4aa08f to
af6c9e8
Compare
|
New changes are detected. LGTM label has been removed. |
|
/retest |
af6c9e8 to
56db128
Compare
|
/test pull-kind-e2e-kubernetes-1-24 |
3 similar comments
|
/test pull-kind-e2e-kubernetes-1-24 |
|
/test pull-kind-e2e-kubernetes-1-24 |
|
/test pull-kind-e2e-kubernetes-1-24 |
|
1.24 seems to be permanently failing https://prow.k8s.io/pr-history/?org=kubernetes-sigs&repo=kind&pr=3419, keep retesting is not going to solve the problem ;) |
Yeahhh but it seems to be not related to my change and I thought it's some CI problem with lack of resources. It was the same with pull-kind-e2e-kubernetes-1-25 which eventually passed. |
BenTheElder
left a comment
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.
... we (=kind approvers) really should've gotten back to this PR a very long time ago, apologies, I have mostly been chasing bug fixes and debugging when I have time, I'm aiming to make sure we keep up with the PR backlog going forward.
I have one minor correction request, if you're not available after some time given the duration we can apply it in a follow-up so as to retain the attribution for this commit.
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: radeksm The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
... So the github "commit suggestion" button broke the CLA :/ |
stmcginnis
left a comment
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.
Sorry this has sat for so long. @radeksm would you be able to update to fix the CLA issues now? If so, we should be able to get this through much faster than it's been.
| "wait", | ||
| time.Duration(0), | ||
| "wait for control plane node to be ready (default 0s)", | ||
| "the length of time to wait for control plane node to be ready (default 0s). Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't wait.", |
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.
Now that this is two full sentences, it would be nice if it started with capitalization.
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.
@stmcginnis maybe at this point send an updated PR, I feel bad for how this went but we also can't merge CLA failures and you're suggesting changes anyhow (and the PR is single line ...)
|
@radeksm: The following tests 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. |
|
/easycla |
Follow up from kubernetes-sigs#3418 and kubernetes-sigs#3419. `kind create cluster --help` does not explain what is the expected format of the `--wait` option. This is described in the quick start, but not in the command line help output. This change adds more a more verbose description to make it more clear. Signed-off-by: Sean McGinnis <[email protected]>
|
Redone with #3992 |
This is just a very minor follow up on this pull request 3418.
kind create cluster --helpdoes not explain what is expected format of --wait option. This is documented well in site/content/docs/user/quick-start.md but this simple change to command line help is going to save some time and confusion.