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.

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

kubectl wait command #29

Open
gimler opened this issue May 19, 2021 · 5 comments
Open

kubectl wait command #29

gimler opened this issue May 19, 2021 · 5 comments
Labels

Comments

@gimler
Copy link

gimler commented May 19, 2021

What is the difference between the wait_for.sh shell script and the kubectl wait command
https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#wait

@groundnuty
Copy link
Owner

groundnuty commented May 19, 2021

To be honest, I just heard of it from you, but after quickly playing with it, for example, it does not allow to wait for a job to complete. On the other hand, it allows waiting for the resource to be deleted.
I would say it's a bit lower level than wait_for.sh, where there is a bit more logic coded to provide useful scenarios.

wait_for.sh could use it internally. It does not, because it was created before kubectl wait existed :-)

@gimler
Copy link
Author

gimler commented May 20, 2021

thanks for clarification. I would be nice if the readme has a small notice about it.

@gimler
Copy link
Author

gimler commented May 26, 2021

@TarekAS
Copy link

TarekAS commented Nov 27, 2022

kubectl wait --for=condition=complete --timeout=30s job/myjob should work as an alternative, though I've yet to try.

It seems experimental though.

@groundnuty
Copy link
Owner

@TarekAS please feel welcome to come back with comments if you happen to test it
k8s-wait script compensates for the shortcomings of kubectl, It would be great to replace parts of it with native kubectl commands!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants