-
Notifications
You must be signed in to change notification settings - Fork 542
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
Azure support in perf-tests and on the dashboard #2771
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
Comments
mboersma
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
Jul 15, 2024
/cc @jackfrancis @Jont828 |
This PR proposes a new Azure 100 node scale test:
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Dec 8, 2024
/remove-lifecycle stale |
k8s-ci-robot
removed
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Dec 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be added:
We would like to add an Azure-based job to the Kubernetes performance dashboard.
Why is this needed:
Another provider in the mix will increase the information available to the Kubernetes community and broaden the test signal available to maintainers and to the release team.
Changes to ClusterLoader2 perf and scalability tests are anticipated, so this seemed a reasonable place to track the effort.
Details:
This is a tracking issue and is purposefully short on detail. We are in the investigation phase currently, and we very much appreciate all the help we've gotten from sig-scalability folks so far!
The text was updated successfully, but these errors were encountered: