Pull request template
Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions
- [ ] 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?
- [ ] Have you considered whether you want to use semantic versioning order?
- [ ] Is your submission signed?
- [ ] Is the operator icon set?
Updates to existing Operators
- [ ] Did you create a
ci.yaml
file according to the update instructions? - [ ] Is your new CSV pointing to the previous version with the
replaces
property if you chosereplaces-mode
via theupdateGraph
property inci.yaml
? - [ ] Is your new CSV referenced in the appropriate channel defined in the
package.yaml
orannotations.yaml
? - [ ] Have you tested an update to your Operator when deployed via OLM?
- [ ] Is your submission signed?
Your submission should not
- [ ] 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-operators
andcommunity-operators
at once - [ ] Modify any files outside the above mentioned folders
- [ ] Contain more than one commit. Please squash your commits.
Operator Description must contain (in order)
- [ ] 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
Operator Metadata should contain
- [ ] Human readable name and 1-liner description about your Operator
- [ ] Valid category name1
- [ ] 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