Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add logic to wait for conditions to be true #863

Closed
yashbhutwala opened this issue Jul 2, 2019 · 9 comments
Closed

Add logic to wait for conditions to be true #863

yashbhutwala opened this issue Jul 2, 2019 · 9 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@yashbhutwala
Copy link

Functionality similar to kubectl wait --for-condition=ready pod -l=labels

Function here in kubernetes e2e test framework is good for reference as well: https://github.com/kubernetes/kubernetes/blob/master/test/e2e/framework/pod/wait.go#L111
@yliaog
Copy link
Contributor

yliaog commented Jul 9, 2019

/cc

@roycaihw roycaihw added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 9, 2019
@roycaihw roycaihw mentioned this issue Aug 28, 2019
Closed
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 7, 2019
@yspreen
Copy link

yspreen commented Oct 25, 2019

Is there any way to achieve this functionality with the current version? Or is it just not possible right now?

@prathameshd9
Copy link

Interested in the wait-for-pod condition. Using 1.10 version..

@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 19, 2019
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

@underyx
Copy link

underyx commented Nov 19, 2020

/reopen

This is still a valid feature request.

@k8s-ci-robot
Copy link
Contributor

@underyx: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

This is still a valid feature request.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@underyx @yashbhutwala @roycaihw @yspreen @k8s-ci-robot @prathameshd9 @fejta-bot @yliaog