Trigger EKS E2E tests with Build Test Artifacts #1937
+50
−10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the issue
There is no mechanism to run the EKS E2E tests prior to a release and the weekly cron job isn't monitored. This overlooks common start-up issues that could occur for the Amazon CloudWatch Observability EKS add-on when providing a configuration using helm.
Description of changes
StartEKSE2ETeststobuild-test-artifacts.yml, which triggerse2e-test.yml.e2e-test.ymlto acceptbuild_run_idandbuild_sha, includeCheckBuildTestArtifacts, and skipBuildAgentifbuild_run_idandbuild_shais provided.License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
View Workflow Run #19091066216
Requirements
Before commiting your code, please do the following steps.
make fmtandmake fmt-shmake lintIntegration Tests
To run integration tests against this PR, add the
ready for testinglabel.