-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 E2E: autoscaler e2e test #8514
Conversation
debff0a
to
e5f3da5
Compare
/test ? |
@ykakarap: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
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/test-infra repository. |
/test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-full-main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a couple of nits from my side.
Also, for the sake of keeping the test matrix simple, what about having only one version of this test using CC?
@killianmuldoon @sbueringer opinions?
test/e2e/data/infrastructure-docker/main/clusterclass-quick-start.yaml
Outdated
Show resolved
Hide resolved
test/e2e/data/infrastructure-docker/main/cluster-template-autoscaler/md.yaml
Outdated
Show resolved
Hide resolved
test/e2e/data/infrastructure-docker/main/cluster-template-autoscaler/md.yaml
Outdated
Show resolved
Hide resolved
Yes please. We are at a point where we almost have to think about how we reduce the number of tests we already have so we should be very very careful when we add new ones. Wondering if this also means that we should implement the test itself only for ClusterClass (to reduce maintenance effort and because we wouldn't test the legacy variant in core CAPI it's very hard to keep the legacy variant of the test working) |
test/e2e/data/autoscaler/autoscaler-to-workload-management.yaml
Outdated
Show resolved
Hide resolved
Q: Does the test already cover all scenarios described in #8282? (I know the PR is WIP) |
test/e2e/data/infrastructure-docker/main/clusterclass-quick-start.yaml
Outdated
Show resolved
Hide resolved
test/e2e/data/infrastructure-docker/main/clusterclass-quick-start.yaml
Outdated
Show resolved
Hide resolved
5c6ce87
to
8c3bdc8
Compare
hey, this looks really cool. i haven't had a chance to review yet, but hopefully i can take look before kubecon. |
@elmiko Just a hint to avoid redundant reviews. It probably makes sense to wait for the next iteration. Addressing the findings above will result in some bigger changes to the PR. |
thanks @sbueringer , i won't rush to review this one just yet. |
8c3bdc8
to
b020fb9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just nits, overall looks good
Also checked that we cover all use cases described in #7293 (comment)
@elmiko If you have some time, should be ready for a round of review. I only found a few nits |
thanks @sbueringer , will make some time this week |
/lgtm pending squash + #8514 (comment) |
LGTM label has been added. Git tree hash: d88a41690f6928993e984d0bb2d3025ab9e935ea
|
/retest |
28023f5
to
6095e3b
Compare
/test pull-cluster-api-e2e-full-main |
/lgtm |
LGTM label has been added. Git tree hash: 1af2731109d68014182c50511401e8320db05af2
|
/lgtm /retest |
The success rate of e2e-full on this PR is really concerning (2 failures, 1 success since yesterday), but I'm pretty sure it's not caused by anything in this PR (xref: https://prow.k8s.io/pr-history/?org=kubernetes-sigs&repo=cluster-api&pr=8514) |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ykakarap and @sbueringer , this is looking really nice, good work! i like how you've structured the tests. i left a couple comments, but they are suggestions not blockers for me.
6095e3b
to
14d3cbb
Compare
/test pull-cluster-api-e2e-full-main |
1 similar comment
/test pull-cluster-api-e2e-full-main |
Thank you very much!! /lgtm |
LGTM label has been added. Git tree hash: 9d5557e402af45d765f0d381b4bd4925888dca03
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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 |
/area e2e-testing |
What this PR does / why we need it:
This PR adds the E2E tests for autoscaler. It tests the configuration in which the autoscaler is deployment on the workload cluster. The autoscaler test works with both classy and legacy Clusters.
Thanks to @fabriziopandini for doing the initial POC on this work.
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 #8282