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

Migrate pull-kubernetes-kubemark-e2e-gce-scale to community-owned infrastructure #24353

Merged
merged 2 commits into from
Nov 15, 2021
Merged

Migrate pull-kubernetes-kubemark-e2e-gce-scale to community-owned infrastructure #24353

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6bd525e
sig-scalability: migrate pull-kubernetes-kubemark-e2e-gce-scale to co…
Nov 15, 2021
2223742
Save prometheus snapshot for pull-kubernetes-kubemark-e2e-gce-scale p…
Nov 15, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions config/jobs/kubernetes/sig-scalability/sig-scalability-presubmit-jobs.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -356,6 +356,7 @@ presubmits:
privileged: true

- name: pull-kubernetes-kubemark-e2e-gce-scale
cluster: k8s-infra-prow-build
always_run: false
max_concurrency: 1
branches:
Expand Down Expand Up @@ -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
Copy link
Member

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?

Copy link
Member Author

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.

- --gcp-zone=us-east1-b
- --kubemark
- --kubemark-nodes=5000
Expand All @@ -404,6 +405,9 @@ presubmits:
- --test_args=--ginkgo.focus=xxxx
- --test-cmd=$GOPATH/src/k8s.io/perf-tests/run-e2e.sh
- --test-cmd-args=cluster-loader2
- --test-cmd-args=--experimental-gcp-snapshot-prometheus-disk=true
- --test-cmd-args=--experimental-prometheus-disk-snapshot-name=$(JOB_NAME)-$(BUILD_ID)
- --test-cmd-args=--experimental-prometheus-snapshot-to-report-dir=true
- --test-cmd-args=--nodes=5000
- --test-cmd-args=--provider=kubemark
- --test-cmd-args=--report-dir=$(ARTIFACTS)
Expand All @@ -412,7 +416,7 @@ presubmits:
- --test-cmd-name=ClusterLoaderV2
- --timeout=1200m
- --use-logexporter
- --logexporter-gcs-path=gs://sig-scalability-logs/$(JOB_NAME)/$(BUILD_ID)
- --logexporter-gcs-path=gs://k8s-infra-scalability-tests-logs/$(JOB_NAME)/$(BUILD_ID)
# TODO(krzyzacy): Figure out bazel built kubemark image
#env:
# - name: KUBEMARK_BAZEL_BUILD
Expand Down