-
Notifications
You must be signed in to change notification settings - Fork 33
Add a script generating files for OperatorHub.io #302
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
Add a script generating files for OperatorHub.io #302
Conversation
✅ Deploy Preview for kubernetes-sigs-kmm ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qbarrand 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 |
Codecov ReportBase: 77.68% // Head: 77.68% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #302 +/- ##
=======================================
Coverage 77.68% 77.68%
=======================================
Files 26 26
Lines 2783 2783
=======================================
Hits 2162 2162
Misses 516 516
Partials 105 105 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
LGTM 👍 |
config/manifests/bases/kernel-module-management.clusterserviceversion.yaml
Show resolved
Hide resolved
/hold |
@qbarrand: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
Currently the firmware path defined in the Module CR is copied into the /var/lib/firmware host path, including the the rightmost directory. Since customed firmware base loading directory for kernel modules is /var/lib/firmware, it means that kernel modules that are expecting their firmware to be located unnder base path (/var/lib/firmware) cannot be run, since current implementation will always contain at leas one additional directory under /var/lib/firmware. This PR changes implementation, so that, if needed, firmware file can be copied directly under the base path (/var/lib/firmware)
4e80757
to
e1ead56
Compare
e1ead56
to
9444d40
Compare
9444d40
to
88f4770
Compare
|
||
Then, use the contents of those directories to create new versions in | ||
[k8s-operatorhub/community-operators](https://github.com/k8s-operatorhub/community-operators). | ||
Only one operator should be affected per pull request; create separate PRs if you want to update both KMM bundles. |
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.
Why is that? Why can't we make a change to both KMM and KMM-hub in a single PR?
Adding a new feature to hub&spoke will probably modify both KMM and KMM-hub.
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.
The checklist when creating a new PR mentions this limitation.
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.
You mean PRs to https://github.com/k8s-operatorhub/community-operators? Do you have some link to the checklist?
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.
The checklist is the default PR template. See k8s-operatorhub/community-operators#2858 for an example
88f4770
to
dd967a9
Compare
CONTRIBUTING.md
Outdated
First, generate all manifests: | ||
|
||
```shell | ||
make operator-hub-release IMAGE_TAG=<RELEASE_TAG> VERSION=<VERSION_NUMBER> |
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.
make operator-hub-release IMAGE_TAG=<RELEASE_TAG> VERSION=<VERSION_NUMBER> | |
make operatorhub-release IMAGE_TAG=<RELEASE_TAG> VERSION=<VERSION_NUMBER> |
Make a few adjustements to the base CSVs.
dd967a9
to
ce3dd98
Compare
/lgtm |
/unhold |
Make a few adjustements to the base CSVs.
/cc @ybettan