test: add WorkloadDeployment HPA lifecycle chainsaw tests - #205
Open
savme wants to merge 1 commit into
Open
Conversation
savme
force-pushed
the
test/workloaddeployment-hpa-chainsaw
branch
from
August 4, 2026 13:56
3e11fed to
fe29066
Compare
Contributor
|
@savme FYI looks like CI is failing on these |
Contributor
Author
|
@scotwells |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds Chainsaw e2e coverage for the
WorkloadDeploymentHPA controller.It also adds a
Taskfilefor e2e-only workflows using the shareddatum-cloud/test-infrasetup. This does not replace the existing Makefile -make test-e2edelegates to the new Taskfile flow.The tests run against a test-infra cluster and verify the controller creates, updates, and removes local HPAs based on
WorkloadDeploymentautoscaling settings. These tests only validate HPA object lifecycle and spec sync. They do not test real scale-up or scale-down behavior yet.