Create a Pull Request

The final step is to create a pull request for the targeted upstream repo.

Procedure

  1. Identify the upstream repository for your target catalog:
    Catalog Upstream Repository

    Certified Catalog

    certified-operators
  2. If you want to publish your Operator bundle in multiple catalogs, create a pull request for each target catalog.
  3. If you are not familiar with creating a pull request in GitHub, see Creating a pull request from a fork.
  4. Create your pull request. The title must conform to the following format: operator my-operator (v1.4.8). It should begin with the word operator followed by your Operator package name, followed by the version number in parenthesis.
    Note

    When you create a pull request it triggers the Red Hat hosted pipeline and provides an update through a pull request comment whenever it has failed or completed.
  5. Follow these guidelines:
    • You can re-trigger the Red Hat hosted pipeline by closing and reopening your pull request.
    • You can only have one open pull request at a time for a given Operator version.
    • Once a pull request has been successfully merged it can not be changed. You have to bump the version of your Operator and open a new pull request.
    • You must use the package name of your Operator as the directory name that you created under operators. This package name should match the package annotation in the annotations.yaml file. This package name should also match the prefix of the clusterserviceversion.yaml filename.
    • Your pull requests should only modify files in a single Operator version directory. Do not attempt to combine updates to multiple versions or updates across multiple Operators.
    • The version indicator used to name your version directory should match the version indicator used in the title of the pull request.
    • Image tags are not accepted for running the certification tests, only SHA digest are used. See Replace all references to image tags with the corresponding SHA digest.