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
Test suite enhancements around WMCO deployments #1620
Test suite enhancements around WMCO deployments #1620
Conversation
@sebsoto: This pull request references WINC-950 which is a valid jira issue. 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. |
Skipping CI for Draft Pull Request. |
Makes the e2e hack script smarter and only deploys the operator if it is not already deployed.
6e3ccbe
to
b48a63e
Compare
/approve cancel |
/test gcp-e2e-operator |
/test aws-e2e-operator |
/test aws-e2e-upgrade |
@sebsoto: No Jira issue is referenced in the title of this pull request. 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. |
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.
Thanks for doing this, @sebsoto. No more disabling the version test when running locally ❤️
@@ -41,6 +42,9 @@ const ( | |||
wmcoContainerName = "manager" | |||
) | |||
|
|||
// versionRegex captures the version from the output of the WMCO version command | |||
var versionRegex = regexp.MustCompile(`version: "([^"]*)"`) |
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.
Please add an example to show what you are matching for
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aravindhp 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 |
Changes the way the tests determine the expected WMCO version. Instead of building the operator locally, and running the version command, the tests will exec into the running WMCO pod and run the version command there. This allows for the tests to run against an operator without having direct access to the source that built the operator. The main importance of this is the tests can now be run against a WMCO which has been installed from a bundle not built by the user. This includes officially released WMCO bundles installed via OperatorHub. This will also enable better upgrade testing, as we will be able to install an operator on the cluster built from a different pipeline and run tests against it. Such as installing a 4.13 operator on a 4.14 cluster, running some tests against it, and then upgrading to the 4.14 operator.
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
/hold Revision 858e3e9 was retested 3 times: holding |
/test aws-e2e-upgrade Some issues installing the operator, investigating. |
/hold cancel |
/hold |
/hold cancel |
@sebsoto: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
/cherry-pick release-4.13 |
/cherry-pick release-4.12 |
@sebsoto: #1620 failed to apply on top of branch "release-4.13":
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. |
@sebsoto: #1620 failed to apply on top of branch "release-4.12":
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. |
/cherry-pick release-4.13 |
@mtnbikenc: new pull request created: #1727 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. |
/cherry-pick release-4.12 |
@mansikulkarni96: new pull request created: #1819 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. |
This is a set of changes which are meant to enable better upgrade testing in CI