-
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
Add job to run ClusterLoader2 load test on 100 node CAPZ cluster #33423
base: master
Are you sure you want to change the base?
Conversation
ccea521
to
ec15cb2
Compare
config/jobs/kubernetes/sig-scalability/sig-scalability-periodic-azure.yaml
Outdated
Show resolved
Hide resolved
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.
checking the K8s version.
config/jobs/kubernetes/sig-scalability/sig-scalability-periodic-azure.yaml
Outdated
Show resolved
Hide resolved
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
@marseel @mborsz @mm4tt @wojtek-t after much iteration this clusterloader2 100 node test configuration works reliably against CAPZ-built Azure clusters running the latest k8s bits. We'd love to contribute this additional infra provider to the perf-dash effort and add muscle to any SIG Scalability infra troubleshooting by donating Azure cycles. |
0c13b82
to
7f40b20
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Jont828 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/remove lifecycle-stale |
d726ed8
to
e6b2b12
Compare
e6b2b12
to
b8d1305
Compare
/remove-lifecycle stale |
This adds a job to provision a CAPZ self managed cluster with 100 nodes to run the CL2 load test. This is provisioned on community infra, and does not use AKS (the Azure provider for CL2 is just named that
--aks
and not--azure
).