-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Migrate pull-kubernetes-kubemark-e2e-gce-scale to community-owned infrastructure #24353
Migrate pull-kubernetes-kubemark-e2e-gce-scale to community-owned infrastructure #24353
Conversation
…mmunity-owned infrastructure
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: marseel 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 |
/lgtm |
@@ -393,7 +394,7 @@ presubmits: | |||
- --flush-mem-after-build=true | |||
- --gcp-node-size=e2-standard-8 | |||
- --gcp-nodes=84 | |||
- --gcp-project=k8s-presubmit-scale | |||
- --gcp-project-type=scalability-project |
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.
Can scalability-project handle 5k-node kubemark?
Don't we want a different class for those projects?
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.
yes, scalability-project can handle 5k kubemarks (our kubemark 5k CI already uses this pool).
We don't have different class right now.
@marseel: 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. |
/assign @tosi3k
Fixes #24349