-
Notifications
You must be signed in to change notification settings - Fork 517
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 sig-scalability jobs to k8s-infra #1898
Comments
Ref: kubernetes/perf-tests#1898 Migrate node throughput tests to community-owned infrastructure Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Ref: kubernetes/perf-tests#1898 Migrate the job ot community-owned infrastructure Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Ref: kubernetes/perf-tests#1898 Migrate to community-owned infrastructure: - ci-benchmark-scheduler-master - ci-benchmark-scheduler-perf-master Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Ref: kubernetes/perf-tests#1898 Migrate to community-owned infrastructure: - ci-benchmark-kube-dns-master - ci-benchmark-nodelocal-dns-master Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Ref: kubernetes/perf-tests#1898 Migrate ci-kubernetes-kubemark-100-gce-scheduler to community-owned infrastructure Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Ref: kubernetes/perf-tests#1898 - Migrate the job to community-owned infrastructure - Switch to generic project-type - change bucket destination for the logs Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Ref: kubernetes/perf-tests#1898 - Migrate the job to community-owned infrastructure - change logs destination bucket - change project used to run the job Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Ref: kubernetes/perf-tests#1898 - Migrate the job to community-owned infrastructure - change logs destination bucket - change project used to run the job Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
After kubernetes/test-infra#23806 ci-kubernetes-kubemark-500-gce started flaking due to quota issues: kubernetes/test-infra#23806 (comment) Can we increase quota in projects used there? |
@mborsz I raised the quota to 84 CPUs where it's needed but I'll take a deeper look at the scalability project pool to align the quotas. |
ci-kubernetes-kubemark-500-gce failed with the same error today:
That run used project: k8s-infra-e2e-boskos-scale-02 Can we increase quota there as well? |
Tests are still flaking: Example today: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-kubemark-500-gce/1447784989184757760 It used k8s-infra-e2e-boskos-scale-02 again. @ameukam, can we increase quota in all projects used in kubemark-500 tests? |
Ref: kubernetes/perf-tests#1898 Migrate: - ci-kubernetes-e2e-gce-network-metric-measurement - ci-kubernetes-e2e-gci-gce-scalability-networkpolicies Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Ref: kubernetes/perf-tests#1898 Migrate to community-owned infrastructure. Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Ref: kubernetes/perf-tests#1898 Migrate to community-owned infrastructure. Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
Related: - Part of: kubernetes/perf-tests#1898 - followup of: kubernetes#24080 Reduce memory allocation to ensure `ci-kubernetes-e2e-gce-scale-correctness` can run on community-owned build clusters. Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". 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. |
Part of umbrella issue to migrate away from google.com gcp projects: kubernetes/k8s.io#1469
We should migrate away from Google scalability projects and use community-owned GCP projects.
We start first with the periodics.
Jobs to be migrated:
Merge-blocking:
Non merge-blocking
ci-benchmark-microbenchmarks: Remove microbenchmarks job test-infra#25999[ ] ci-golang-tip-k8s-1-18: Update Golang jobs test-infra#24035/sig k8s-infra
/sig scalability
/sig testing
The text was updated successfully, but these errors were encountered: