-
Notifications
You must be signed in to change notification settings - Fork 24
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
Refactor bundling for upstream operatorhub releases #363
Conversation
Codecov Report
@@ Coverage Diff @@
## main #363 +/- ##
=======================================
Coverage 53.58% 53.58%
=======================================
Files 45 45
Lines 5488 5488
=======================================
Hits 2941 2941
- Misses 2337 2338 +1
+ Partials 210 209 -1
Flags with carried forward coverage won't be shown. Click here to find out more. |
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, thanks!
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jotak 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 |
Bundling on upstream k8S operatorhub was broken for a while (we didn't release 1.0.2 as we did on openshift's operatorhub)
These changes bring back a non-openshift OLM bundle target (it allowed to get this PR merged: k8s-operatorhub/community-operators#2850 )
The tl;dr is: kustomize files have been moved around to permit building two different OLM bundles, the one for openshift as usual (e.g. with
make bundle-update
as usual) and the one for https://github.com/k8s-operatorhub/community-operators, withBUNDLE_CONFIG=config/k8s-olm make bundle-update
I've also added some automation around the operatorhub release (
make prepare-operatorhub
) and updated the RELEASE.md doc