-
Notifications
You must be signed in to change notification settings - Fork 60
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
release: changes to publish 0.10.0 in operator hub #453
release: changes to publish 0.10.0 in operator hub #453
Conversation
Updated the operator hub bundle for the 0.10.0 release. First bumped VERSION in Makefile then the new bundle was generated as: ``` $ make bundle IMG=quay.io/confidential-containers/operator:v0.10.0 ``` Signed-off-by: Chris Porter <[email protected]>
fa26515
to
fca91a3
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.
@portersrc thanks for working on this too!
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 @portersrc!
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, I especially appreciate the commit message.
@portersrc I'm not sure if this can be merged already or if it should wait for k8s-operatorhub/community-operators#5081 ? |
Hi @ldoktor !
Usually I wait the PR to community-operators get merged first. I just ping'ed Jens to approve it. And I will send a commit there to add myself as an owner of the operator on the hub to speed up the release process. |
Thanks, I thought so as (even such late in the process) someone might require a change which would have to be reflected here. Anyway it's merged already so let me merge this one as well... |
I submitted the k8s-operatorhub/community-operators#5081 to publish 0.10.0 bundle in operator hub. After it is merged, coco's operator landing page in hub should get updated (see https://operatorhub.io/operator/cc-operator).
Here I'm sending the changes I did to publish it.