Thanks submitting your Operator. Please check below list before you create your Pull Request.
Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.
- Does your operator have nested directory structure?
- Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
- Are you familiar with our contribution guidelines?
- Have you packaged and deployed your Operator for Operator Framework?
- Have you tested your Operator with all Custom Resource Definitions?
- Have you tested your Operator in all supported installation modes?
- Is your submission signed?
- Is your new CSV pointing to the previous version with the
replacesproperty? - Is your new CSV referenced in the appropriate channel defined in the
package.yaml? - Have you tested an update to your Operator when deployed via OLM?
- Is your submission signed?
- Modify more than one operator
- Modify an Operator you don't own
- Rename an operator - please remove and add with a different name instead
- Submit operators to both
upstream-community-operatorsandcommunity-operatorsat once - Modify any files outside the above mentioned folders
- Contain more than one commit. Please squash your commits.
- Description about the managed Application and where to find more information
- Features and capabilities of your Operator and how to use it
- Any manual steps about potential pre-requisites for using your Operator
- Human readable name and 1-liner description about your Operator
- Valid category name1
- One of the pre-defined capability levels2
- Links to the maintainer, source code and documentation
- Example templates for all Custom Resource Definitions intended to be used
- A quadratic logo
Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here
