Skip to content

Add VMSS-based scalability test templates #5784

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

Merged
merged 4 commits into from
Jul 25, 2025

Conversation

nojnhuh
Copy link
Contributor

@nojnhuh nojnhuh commented Jul 23, 2025

What type of PR is this?
/kind feature

What this PR does / why we need it:

This PR adds load templates with VMSS-based worker nodes, for clusters both with and without DRA.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

TODOs:

  • squashed commits
  • includes documentation
  • adds unit tests
  • cherry-pick candidate

Release note:

NONE

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/feature Categorizes issue or PR as related to a new feature. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jul 23, 2025
@k8s-ci-robot k8s-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Jul 23, 2025
@@ -138,6 +138,8 @@ select_cluster_template() {
export CLUSTER_TEMPLATE="${CLUSTER_TEMPLATE/custom-builds/custom-builds-machine-pool}"
fi
fi

export CLUSTER_TEMPLATE="test/dev/cluster-template-custom-builds-machine-pool-load-dra.yaml"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I intend to drop this and configure it in test-infra once we're confident here that it will work.

/test pull-cluster-api-provider-azure-load-test-dra-with-workload-custom-builds

@nojnhuh nojnhuh force-pushed the load-vmss-template branch from 377091c to 45c51e7 Compare July 23, 2025 21:00
@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 23, 2025

/test pull-cluster-api-provider-azure-load-test-dra-with-workload-custom-builds

Copy link

codecov bot commented Jul 23, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@5605fb5). Learn more about missing BASE report.
⚠️ Report is 7 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5784   +/-   ##
=======================================
  Coverage        ?   52.94%           
=======================================
  Files           ?      279           
  Lines           ?    29666           
  Branches        ?        0           
=======================================
  Hits            ?    15706           
  Misses          ?    13147           
  Partials        ?      813           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 23, 2025

/test pull-cluster-api-provider-azure-load-test-dra-with-workload-custom-builds

@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 23, 2025

/test ?

@k8s-ci-robot
Copy link
Contributor

@nojnhuh: The following commands are available to trigger required jobs:

/test pull-cluster-api-provider-azure-apiversion-upgrade
/test pull-cluster-api-provider-azure-build
/test pull-cluster-api-provider-azure-ci-entrypoint
/test pull-cluster-api-provider-azure-e2e
/test pull-cluster-api-provider-azure-e2e-aks
/test pull-cluster-api-provider-azure-test
/test pull-cluster-api-provider-azure-verify

The following commands are available to trigger optional jobs:

/test pull-cluster-api-provider-azure-apidiff
/test pull-cluster-api-provider-azure-apiserver-ilb
/test pull-cluster-api-provider-azure-capi-e2e
/test pull-cluster-api-provider-azure-conformance
/test pull-cluster-api-provider-azure-conformance-custom-builds
/test pull-cluster-api-provider-azure-conformance-dual-stack-with-ci-artifacts
/test pull-cluster-api-provider-azure-conformance-ipv6-with-ci-artifacts
/test pull-cluster-api-provider-azure-conformance-with-ci-artifacts
/test pull-cluster-api-provider-azure-conformance-with-ci-artifacts-dra
/test pull-cluster-api-provider-azure-dra-scalability
/test pull-cluster-api-provider-azure-e2e-optional
/test pull-cluster-api-provider-azure-e2e-workload-upgrade
/test pull-cluster-api-provider-azure-load-test-1k-dra-with-workload-custom-builds
/test pull-cluster-api-provider-azure-load-test-custom-builds
/test pull-cluster-api-provider-azure-load-test-dra-custom-builds
/test pull-cluster-api-provider-azure-load-test-dra-with-workload-custom-builds
/test pull-cluster-api-provider-azure-perf-test-apiserver-availability
/test pull-cluster-api-provider-azure-windows-custom-builds
/test pull-cluster-api-provider-azure-windows-with-ci-artifacts

Use /test all to run the following jobs that were automatically triggered:

pull-cluster-api-provider-azure-apidiff
pull-cluster-api-provider-azure-build
pull-cluster-api-provider-azure-ci-entrypoint
pull-cluster-api-provider-azure-conformance
pull-cluster-api-provider-azure-conformance-custom-builds
pull-cluster-api-provider-azure-conformance-dual-stack-with-ci-artifacts
pull-cluster-api-provider-azure-conformance-ipv6-with-ci-artifacts
pull-cluster-api-provider-azure-conformance-with-ci-artifacts
pull-cluster-api-provider-azure-conformance-with-ci-artifacts-dra
pull-cluster-api-provider-azure-e2e
pull-cluster-api-provider-azure-e2e-aks
pull-cluster-api-provider-azure-e2e-workload-upgrade
pull-cluster-api-provider-azure-test
pull-cluster-api-provider-azure-verify

In response to this:

/test ?

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-sigs/prow repository.

@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 23, 2025

/test pull-cluster-api-provider-azure-load-test-1k-dra-with-workload-custom-builds

1 similar comment
@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 24, 2025

/test pull-cluster-api-provider-azure-load-test-1k-dra-with-workload-custom-builds

@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 24, 2025

/test pull-cluster-api-provider-azure-load-test-1k-dra-with-workload-custom-builds

@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 24, 2025

/test pull-cluster-api-provider-azure-load-test-dra-with-workload-custom-builds

2 similar comments
@jackfrancis
Copy link
Contributor

/test pull-cluster-api-provider-azure-load-test-dra-with-workload-custom-builds

@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 24, 2025

/test pull-cluster-api-provider-azure-load-test-dra-with-workload-custom-builds

@@ -88,6 +88,7 @@ setup() {
if [[ -z "${CLUSTER_TEMPLATE:-}" ]]; then
select_cluster_template
fi
export CLUSTER_TEMPLATE="test/dev/cluster-template-custom-builds-machine-pool-load-dra.yaml"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/hold

Reminder to remove this as soon as the test-infra job sets this.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kubernetes/test-infra#35212

We can update periodic jobs after this merges, I reckon.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 24, 2025
@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 24, 2025

I need to clean up the commit history here, but this should be representative of the changes I intend to merge here aside from the CLUSTER_TEMPLATE override in ci-entrypoint.

/retitle Add VMSS-based scalability test templates

@k8s-ci-robot k8s-ci-robot changed the title WIP: Add VMSS-based scalability test templates Add VMSS-based scalability test templates Jul 24, 2025
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 24, 2025
@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 24, 2025

/test pull-cluster-api-provider-azure-load-test-dra-with-workload-custom-builds

@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 25, 2025

/test pull-cluster-api-provider-azure-load-test-dra-with-workload-custom-builds

1 similar comment
@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 25, 2025

/test pull-cluster-api-provider-azure-load-test-dra-with-workload-custom-builds

@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 25, 2025

Watching in the portal, it seemed some VMSS instances were failing to provision due to an Azure internal error, although the k8s Node objects were all already Ready. I noticed after the test had already timed out and was collecting logs, the VMSS did eventually recover to 100/100 successful instances. This case I think is anomalous enough that it's probably not worth budgeting for by increasing timeouts.

/test pull-cluster-api-provider-azure-load-test-dra-with-workload-custom-builds
/test pull-cluster-api-provider-azure-e2e-workload-upgrade

@willie-yao
Copy link
Contributor

/retest

@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 25, 2025

@willie-yao That test is flaky on main too. I think I need to take a look at the config, but this PR shouldn't be affecting that.

@nojnhuh nojnhuh force-pushed the load-vmss-template branch from f0b6b10 to f23d80f Compare July 25, 2025 06:14
@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 25, 2025

/test pull-cluster-api-provider-azure-load-test-dra-with-workload-custom-builds

@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 25, 2025

This is all cleaned up now and ready for review. Keeping the /hold until we see the DRA load test pass with this particular set of changes.

@nojnhuh nojnhuh force-pushed the load-vmss-template branch from f23d80f to f0476f1 Compare July 25, 2025 06:28
@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 25, 2025

/test pull-cluster-api-provider-azure-load-test-dra-with-workload-custom-builds

@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jul 25, 2025

DRA load test passed.

/hold cancel
/assign @jackfrancis

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 25, 2025
@willie-yao
Copy link
Contributor

/retest

@k8s-ci-robot
Copy link
Contributor

@nojnhuh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-cluster-api-provider-azure-load-test-1k-dra-with-workload-custom-builds 209ea26 link false /test pull-cluster-api-provider-azure-load-test-1k-dra-with-workload-custom-builds
pull-cluster-api-provider-azure-conformance-with-ci-artifacts-dra f0476f1 link false /test pull-cluster-api-provider-azure-conformance-with-ci-artifacts-dra

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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-sigs/prow repository. I understand the commands that are listed here.

@jackfrancis
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 25, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: b18a4bcb78ac8b78b4281c803507b8a8f4f79d58

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jackfrancis

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 25, 2025
@k8s-ci-robot k8s-ci-robot merged commit 1e22684 into kubernetes-sigs:main Jul 25, 2025
29 of 30 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Jul 25, 2025
@github-project-automation github-project-automation bot moved this from Todo to Done in CAPZ Planning Jul 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants