-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
clusterctl init does not wait for providers to be ready #3720
Comments
@benmoss: The label(s) 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. |
I can take a look into this. |
Just an update. |
/lifecycle active |
/milestone v0.3.11 |
/milestone v0.4.0 |
Closing, see #3825 (comment) |
/close |
@vincepri: Closing this issue. 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. |
What steps did you take and what happened:
What did you expect to happen:
The commands should work sequentially without the user needing to wait or check to make sure pods have started.
Anything else you would like to add:
/kind bug
/area clusterctl
The text was updated successfully, but these errors were encountered: