-
Notifications
You must be signed in to change notification settings - Fork 2
Test cluster chart PR #641 #1529
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
base: main
Are you sure you want to change the base?
Conversation
|
Note As this is a draft PR no triggers from the PR body will be handled. If you'd like to trigger them while draft please add them as a PR comment. |
|
/run cluster-test-suites TARGET_SUITES=./providers/capa/china |
cluster-test-suites
✅ Passed test suitesCAPA China Suite ✅
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a
Available Test SuitesBy default, only the standard test suite runs to reduce costs. If your changes affect specialized environments, you can specify additional test suites: AWS (CAPA) Test Suites
How to Specify Additional Test Suites# Run specific test suites
/run cluster-test-suites TARGET_SUITES=./providers/capa/standard,./providers/capa/china
# Run all test suites for CAPA
/run cluster-test-suites TARGET_SUITES=./providers/capa/
# Run upgrade tests
/run cluster-test-suites TARGET_SUITES=./providers/capa/upgrade,./providers/capa/upgrade-majorNote: Full test suites run automatically on releases. You are responsible for testing all relevant flavors before merging. |
|
/run cluster-test-suites TARGET_SUITES=./providers/capa/karpenter |
cluster-test-suites
❌ Failed test suitesCAPA Karpenter Suite ❌
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a
Available Test SuitesBy default, only the standard test suite runs to reduce costs. If your changes affect specialized environments, you can specify additional test suites: AWS (CAPA) Test Suites
How to Specify Additional Test Suites# Run specific test suites
/run cluster-test-suites TARGET_SUITES=./providers/capa/standard,./providers/capa/china
# Run all test suites for CAPA
/run cluster-test-suites TARGET_SUITES=./providers/capa/
# Run upgrade tests
/run cluster-test-suites TARGET_SUITES=./providers/capa/upgrade,./providers/capa/upgrade-majorNote: Full test suites run automatically on releases. You are responsible for testing all relevant flavors before merging. |
|
There were differences in the rendered Helm template, please check! Output |
|
/run cluster-test-suites TARGET_SUITES=./providers/capa/karpenter,./providers/capa/china |
cluster-test-suites
✅ Passed test suitesCAPA China Suite ✅
CAPA Karpenter Suite ✅
📋 View full results in Tekton Dashboard Rerun trigger: Tip To only re-run the failed test suites you can provide a
Available Test SuitesBy default, only the standard test suite runs to reduce costs. If your changes affect specialized environments, you can specify additional test suites: AWS (CAPA) Test Suites
How to Specify Additional Test Suites# Run specific test suites
/run cluster-test-suites TARGET_SUITES=./providers/capa/standard,./providers/capa/china
# Run all test suites for CAPA
/run cluster-test-suites TARGET_SUITES=./providers/capa/
# Run upgrade tests
/run cluster-test-suites TARGET_SUITES=./providers/capa/upgrade,./providers/capa/upgrade-majorNote: Full test suites run automatically on releases. You are responsible for testing all relevant flavors before merging. |
Warning
DO NOT MERGE! This PR has been created automatically by @taylorbot on behalf of Xander Grzywinski (@salaxander).
Changes
Update the cluster chart version from
4.2.0to4.2.0-60ad078ce5ba2ca54ac63a4d0db66683a16c1714in order to test @salaxander's cluster chart pull request giantswarm/cluster#641.Cluster chart pull request title:
enable NodeRestriction admission control by default.Testing
Please comment this pull request with
/run cluster-test-suitesin order to run e2e tests.