-
Notifications
You must be signed in to change notification settings - Fork 683
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
Let's use kind for cluster creation instead of spinning up a new cluster #127
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. |
Stale issues rot after 30d 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. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@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. |
…ces/release-4.18 Update Konflux references
As of now, we are spinning up a new cluster on GCE for descheduler e2es, we should explore other alternatives to this. https://github.com/kubernetes-sigs/kind seems really easy to setup and run tests against. The problem I notice as of now is it doesn't support a multi-node cluster but this feature is actively being worked on kubernetes-sigs/kind#147, we can wait for this to land before we make switch.
The text was updated successfully, but these errors were encountered: