- Notifications
You must be signed in to change notification settings - Fork542
Production catalog for Red Hat Certified Operator Bundles
License
redhat-openshift-ecosystem/certified-operators
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
Production catalog for Red Hat Certified Operator Bundles
See ourdocumentation tofind out more about Certified operators and contribution.
A new operator bundle submission needs to follow a predefined directorystructure that is described below in this section. The new submission isdone through Github pull requests which can be either open by theCI pipeline ormanually by a user. The recommended way is to use the CI pipeline because it makessure all necessary data are provided in the correct format. Documentation about howto use the pipeline is available in the pipeline repository.
A pull request with a new operator bundle needs to follow given rules to pass a tests:
- Title format:
operator package-name (version)
- Pull request can only modify one operator
- Pull request can't modify already merged operators
- Associated images need to be pinned to specific image digest - tags are not allowed
Rules mentioned above are always followed when pull request is opened using CI pipeline.
This repository contains anoperator
directory where all certified operatorsare stored. Each operator has its directory with its package name. Inside the directory,you have to provide aci.yaml
file that stores the necessary metadata for a successfulcertification process. The format of the file is described below.
operators└── kogito-operator ├── 1.6.0 │ ├── manifests │ │ ├── app.kiegroup.org_kogitobuilds.yaml │ │ ├── app.kiegroup.org_kogitoinfras.yaml │ │ ├── app.kiegroup.org_kogitoruntimes.yaml │ │ ├── app.kiegroup.org_kogitosupportingservices.yaml │ │ ├── kogito-operator.clusterserviceversion.yaml │ │ └── kogito-operator-controller-manager_v1_serviceaccount.yaml │ └── metadata │ └── annotations.yaml └── ci.yaml
In the file, user needs to provide necessary details for the operator certification process.Currently, the certification process supports the following options:
cert_project_id
- Identifier of certification project created through Red Hat Connect.merge
- A boolean value that determines whether a new operator is automaticallymerged when passed all required checks. (optional, default:True
)
About
Production catalog for Red Hat Certified Operator Bundles
Resources
License
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Releases
Packages0
Uh oh!
There was an error while loading.Please reload this page.