-
Notifications
You must be signed in to change notification settings - Fork 196
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
Document the current process for testing new operator bundle versions #1544
Document the current process for testing new operator bundle versions #1544
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1544 +/- ##
=======================================
Coverage 63.38% 63.38%
=======================================
Files 176 176
Lines 11669 11669
=======================================
Hits 7396 7396
Misses 3609 3609
Partials 664 664 Continue to review full report at Codecov.
|
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.
Left some clarification comments/questions but LGTM overall!
b3863b6
to
7713a7e
Compare
In the future this should be automated but I wanted to capture the steps before trying to do that.
Otherwise if generation has been run before and after a release you can end up with two cluster service version files in the bundle which will prevent it from installing correctly.
7713a7e
to
8d44eaa
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.
Updates look good.
What this PR does / why we need it:
This documents the process for building a bundle image, testing upgrading from the previous version and creating the PRs to publish it to the two stores. The process is fiddly and should be automated but I wanted to get the details documented first.
How does this PR make you feel:
If applicable: