Skip to content
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

doc: Procedure to Publish Operator on OperatorHub #225

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

adambkaplan
Copy link
Member

@adambkaplan adambkaplan commented Jul 8, 2024

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

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

NONE

@pull-request-size pull-request-size bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 8, 2024
@openshift-ci openshift-ci bot added release-note-none kind/documentation Categorizes issue or PR as related to documentation. labels Jul 8, 2024
@openshift-ci openshift-ci bot requested review from jkhelil and qu1queee July 8, 2024 18:19
Copy link
Contributor

openshift-ci bot commented Jul 8, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from adambkaplan. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@adambkaplan adambkaplan added this to the release-v0.14.0 milestone Jul 8, 2024
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.

Signed-off-by: Adam Kaplan <[email protected]>
@adambkaplan adambkaplan force-pushed the release-procedure-operatorhub branch from 70d8acb to d36e134 Compare July 9, 2024 14:36
@pull-request-size pull-request-size bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. release-note-none size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

Document/automate how to add/release the operator to operatorhub
1 participant