Skip to content

Enable autoscaling tests for CAPZ (Azure) provider#972

Draft
iuriaranda wants to merge 3 commits intomainfrom
capz-enable-autoscaling-tests
Draft

Enable autoscaling tests for CAPZ (Azure) provider#972
iuriaranda wants to merge 3 commits intomainfrom
capz-enable-autoscaling-tests

Conversation

@iuriaranda
Copy link
Copy Markdown
Contributor

Summary

  • Remove AutoScalingSupported = false override from all three CAPZ test suites (standard, private, upgrade)
  • Add missing scale_helloworld_values.yaml test data files for standard and upgrade suites
  • The default NewTestConfigWithDefaults() already sets AutoScalingSupported: true

Test plan

  • Verify CAPZ standard, private, and upgrade test suites compile
  • Confirm autoscaling scale test runs successfully against a CAPZ cluster with cluster-autoscaler deployed

🤖 Generated with Claude Code

Remove the AutoScalingSupported=false override from all CAPZ test
suites and add missing scale_helloworld_values.yaml test data files.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
@iuriaranda iuriaranda self-assigned this Mar 25, 2026
@iuriaranda
Copy link
Copy Markdown
Contributor Author

TODO

@iuriaranda
Copy link
Copy Markdown
Contributor Author

/run cluster-test-suites VERSION_OVERRIDES=cluster-autoscaler-app=v1.34.3-2,cluster-azure=6.1.0-60048fae9a419e10010b7f3a018f8009a73d3d13 TARGET_SUITES=./providers/capz/standard,./providers/capz/upgrade,./providers/capz/private

@tinkerers-ci
Copy link
Copy Markdown

tinkerers-ci Bot commented Apr 1, 2026

Important

Some test suites failed. See the Checks tab for detailed results per suite.

Re-run only the failed tests:

/run cluster-test-suites TARGET_SUITES=./providers/capz/private,./providers/capz/standard,./providers/capz/upgrade

@iuriaranda
Copy link
Copy Markdown
Contributor Author

/run cluster-test-suites TARGET_SUITES=./providers/capz/standard,./providers/capz/upgrade,./providers/capz/private RELEASE_VERSION=v35.0.0-iuri

@tinkerers-ci
Copy link
Copy Markdown

tinkerers-ci Bot commented Apr 1, 2026

Important

Some test suites failed. See the Checks tab for detailed results per suite.

Re-run only the failed tests:

/run cluster-test-suites TARGET_SUITES=./providers/capz/private,./providers/capz/standard

@tinkerers-ci
Copy link
Copy Markdown

tinkerers-ci Bot commented Apr 1, 2026

Oh No! 😱 At least one test suite has failed during the AfterSuite cleanup stage and might have left around some resources on the MC!

Be sure to check the full results in Tekton Dashboard to see which test suite has failed and then run the following on the associated MC to list all leftover resources:

PIPELINE_RUN="pr-cluster-test-suites-972-cluster-test-suites875jn"

NAMES="$(kubectl api-resources --verbs list -o name | tr '\n' ,)"
kubectl get "${NAMES:0:${#NAMES}-1}" --show-kind --ignore-not-found -l cicd.giantswarm.io/pipelinerun=${PIPELINE_RUN} -A 2>/dev/null

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant