doc: Procedure to Publish Operator on OperatorHub #225
Conversation
pull-request-size
bot
added
the
size/M
openshift-ci
bot
added
release-note-none
kind/documentation
adambkaplan
force-pushed
the
release-procedure-operatorhub
branch
from
70d8acb to
d36e134
Compare
pull-request-size
bot
added
size/L
|
cc @HeavyWombat @SaschaSchwarze0 @ayushsatyam146 can one of you please review? I'd like to use the script for the v0.14.0 operator release. Thanks! |
|
@adambkaplan this looks good but I don't think I can verify it since I don't have Approver/Maintainer permissions. |
|
/approve I think I can self-approve. Needs |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adambkaplan 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 |
openshift-ci
bot
added
the
approved
|
/lgtm |
Add a procedure and script to publish an operator release to the upstream k8s community operators OperatorHub. The script requires the user to fork the upstream k8s operators repsository and afterwards submit a pull request by hand. The script also supports releasing to any catalog that uses the OperatorHub file structure. In the future this procedure/script can be added to our release automation so when an operator release is published, we initiate the process to update the upstream OperatorHub catalog. Co-authored-by: Sascha Schwarze <schwarzs@de.ibm.com> Signed-off-by: Adam Kaplan <adam.kaplan@redhat.com>
|
Moving this to v0.15.0. I'm going to experiment with the script in this PR on the v0.14.0 release to make sure it works. Upstream has been moving towards using file-based catalogs, so the script might be obsolete. |
adambkaplan
force-pushed
the
release-procedure-operatorhub
branch
from
eb3e755 to
2b89b56
Compare
|
New changes are detected. LGTM label has been removed. |
Changes
Add a procedure and script to publish an operator release to the upstream k8s community operators OperatorHub. The script requires the user to fork the upstream k8s operators repsository and afterwards submit a pull request by hand.
In the future this procedure/script can be added to our release automation so when an operator release is published, we initiate the process to update the upstream OperatorHub catalog.
Fixes #132
/kind documentation
Submitter Checklist
See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes