-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
fix: Update minikube prow job to use community cluster #29724
Conversation
@kubernetes/sig-cluster-lifecycle-leads for this transition to the community owned cluster, CPU/memory reqs and limits are required. I've set them initially to .5CPU and 2GB respectively. Let me know if this seems apropriate. |
/hold for review from @kubernetes/sig-cluster-lifecycle-leads |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: neolit123, rjsadow The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Ricky Sadowski <richard.j.sadowski@gmail.com>
/remove-hold |
/lgtm |
@rjsadow: Updated the
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. |
This PR transitions the
pull-minikube-build
job from thedefault
cluster toeks-prow-build-cluster
ref: #29722