Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Migrate sig-scalability jobs to k8s-infra #1898

Closed
19 of 24 tasks
ameukam opened this issue Sep 24, 2021 · 12 comments
Closed
19 of 24 tasks

Migrate sig-scalability jobs to k8s-infra #1898

ameukam opened this issue Sep 24, 2021 · 12 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. sig/testing Categorizes an issue or PR as relevant to SIG Testing.

Comments

@ameukam
Copy link
Member

ameukam commented Sep 24, 2021 •
edited

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

/sig k8s-infra
/sig scalability
/sig testing
@ameukam ameukam added the kind/bug Categorizes issue or PR as related to a bug. label Sep 24, 2021
@k8s-ci-robot k8s-ci-robot added sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. sig/testing Categorizes an issue or PR as relevant to SIG Testing. labels Sep 24, 2021
@ameukam ameukam mentioned this issue Sep 27, 2021
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Sep 27, 2021
@ameukam
Migrated node throughput tests
8ddef87 
Ref: kubernetes/perf-tests#1898

Migrate node throughput tests to community-owned infrastructure

Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
@ameukam ameukam mentioned this issue Sep 27, 2021
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Sep 27, 2021
@ameukam
sig-scalability: migrate ci-perf-tests-kubemark-100-benchmark
3f560aa 
Ref: kubernetes/perf-tests#1898

Migrate the job ot community-owned infrastructure

Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
@ameukam ameukam mentioned this issue Sep 27, 2021
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Sep 27, 2021
@ameukam
sig-scalability: migrate scheduler benchmark tests
48c2780 
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>
@ameukam ameukam mentioned this issue Sep 27, 2021
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Sep 27, 2021
@ameukam
sig-scalability: migrate dns benchmark jobs
a00ffaa 
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>
@ameukam ameukam mentioned this issue Sep 27, 2021
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Sep 29, 2021
@ameukam
sig-scalability : migrate ci-kubernetes-kubemark-100-gce-scheduler
e86d99a 
Ref: kubernetes/perf-tests#1898

Migrate ci-kubernetes-kubemark-100-gce-scheduler to community-owned
infrastructure

Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
@ameukam ameukam mentioned this issue Sep 29, 2021
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Sep 29, 2021
@ameukam
sig-scalability: migrate ci-kubernetes-kubemark-500-gce
86e81c6 
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>
@ameukam ameukam mentioned this issue Sep 29, 2021
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Sep 29, 2021
@ameukam
sig-scalability: migrate ci-kubernetes-e2e-gce-scale-performance
7b35ab8 
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>
@ameukam ameukam mentioned this issue Sep 29, 2021
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Sep 29, 2021
@ameukam
sig-scalability: migrate ci-kubernetes-e2e-gce-scale-performance
5fc3366 
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>
@ameukam ameukam mentioned this issue Sep 30, 2021
Merged
@mborsz
Copy link
Member

mborsz commented Oct 7, 2021

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?

@ameukam
Copy link
Member Author

ameukam commented Oct 7, 2021 •
edited

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.

@ameukam ameukam mentioned this issue Oct 7, 2021
Closed
@mborsz
Copy link
Member

mborsz commented Oct 8, 2021

@ameukam

ci-kubernetes-kubemark-500-gce failed with the same error today:

 - Quota 'CPUS' exceeded.  Limit: 72.0 in region us-central1.

https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-kubemark-500-gce/1446454273704464384

That run used project: k8s-infra-e2e-boskos-scale-02

Can we increase quota there as well?

@mborsz
Copy link
Member

mborsz commented Oct 12, 2021

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?

ameukam added a commit to ameukam/test-infra that referenced this issue Oct 21, 2021
@ameukam
sig-scalability: migrate some e2e tests
9832713 
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>
@ameukam ameukam mentioned this issue Oct 21, 2021
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Oct 21, 2021
@ameukam
sig-scalability: migrate e2e-gce-scale-correctness
1121fde 
Ref: kubernetes/perf-tests#1898

Migrate to community-owned infrastructure.

Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
@ameukam ameukam mentioned this issue Oct 21, 2021
Merged
ameukam added a commit to ameukam/test-infra that referenced this issue Nov 15, 2021
@ameukam
sig-scalability: migrate e2e-gce-scale-correctness
a6fbb0f 
Ref: kubernetes/perf-tests#1898

Migrate to community-owned infrastructure.

Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
ameukam added a commit to ameukam/test-infra that referenced this issue Nov 17, 2021
@ameukam
sig-scalability: reduce memory request for gce-scale-correctness
862b2a4 
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>
@ameukam ameukam mentioned this issue Nov 17, 2021
Merged
@spiffxp spiffxp mentioned this issue Nov 24, 2021
Closed
7 tasks
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 13, 2022
@ameukam
Copy link
Member Author

ameukam commented Feb 14, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 14, 2022
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 22, 2022
@ameukam
Copy link
Member Author

ameukam commented May 23, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 23, 2022
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 21, 2022
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 20, 2022
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

@k8s-ci-robot k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 20, 2022
@k8s-ci-robot
Copy link
Contributor

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ameukam @mborsz @k8s-ci-robot @k8s-triage-robot