-
Notifications
You must be signed in to change notification settings - Fork 159
Use client-go to deploy & wait rather than shell scripts #625
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
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@fejta-bot: 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. |
deploy/kubernetes and test/k8s-integration share some bash scripts for deploying the driver as well as waiting for the deployment to be ready (deploy/kuberntetes/wait-for-deploy.sh; test/k8s-integration/prepull-image.sh).
We should move as much of that as possible to client-go and do it in code rather than shell scripts which are much harder to test & maintain.
The text was updated successfully, but these errors were encountered: