Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Create a separate GH workflow to validate the Operator upgrade #414

Closed
vprashar2929 opened this issue Jul 31, 2024 · 1 comment
Closed

Create a separate GH workflow to validate the Operator upgrade #414

vprashar2929 opened this issue Jul 31, 2024 · 1 comment
Assignees
@vprashar2929

Comments

@vprashar2929
Copy link
Collaborator

Currently, we have an e2e test that deploys a released Operator and then does an upgrade using the bundle/operator build using the PR changes. It only sees if the upgrade is successful and continues running the e2e's It would be nice to have a separate workflow that is specifically responsible for only validating the Upgrade paths and scenarios like running the upgrade once the released operator is deployed and Kepler CR also created etc. Also we can expand the test scope in future as and when new features are added
@vprashar2929 vprashar2929 self-assigned this Jul 31, 2024
@vprashar2929 vprashar2929 mentioned this issue Aug 1, 2024
Merged
@vprashar2929
Copy link
Collaborator Author

closing as #415 was merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vprashar2929 vprashar2929

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vprashar2929