-
Notifications
You must be signed in to change notification settings - Fork 25
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
Implement adopted cluster e2e tests #855
Conversation
58ea636
to
4d0a763
Compare
LGTM, the PR needs to be rebased and wait for the e2e-CI POW after the renaming to execute the tests |
fed227b
to
0a94ef0
Compare
c551da8
to
88ed748
Compare
88ed748
to
2dd6b77
Compare
f3ddbf1
to
ccb3aa7
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.
E2E tests are failing due to a “not ready” clustertemplate error.
@kylewuolle, could you please double-check if the cluster templates readiness verification is functioning as expected? Based on the E2E testing logs, it seems that either the readiness check for the templates wasn’t executed, or it completed too early before the templates were actually ready.
It's confusing but the e2e test process for now is:
So basically we have to wait for this to merge to see the results. I believe this is done so you can't steal secrets by creating a PR and changing the e2e test code since the PR would be reviewed first. |
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.
LGTM.
Will merge without waiting for the tests, because of the checkout issue
This adds adopted cluster e2e tests to the suite. Also, I've ported in the various fixes around timing issues like waiting for the cluster templates to be valid and the credentials to be ready before creating deployments. Resolves #828, #339 and #871