fixes #15

[raffaelespazzoli]

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?

Updates to existing Operators

• Is your new CSV pointing to the previous version with the replaces property?

not sure what this means, where can I find more info

• 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?
  no, how do I do that?

Your submission should not

• Modify more than one operator
• Submit operators to both upstream-community-operators and community-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)

1. Description about the managed Application and where to find more information
2. Features and capabilities of your Operator and how to use it
3. 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 name¹
• One of the pre-defined capability levels²
• 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.

--

¹ If you feel your Operator does not fit any of the pre-defined categories, file a PR against this repo and explain your need

² For more information see here

[openshift-ci-robot]

Hi @raffaelespazzoli. Thanks for your PR.

I'm waiting for a operator-framework or openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dmesser]

@raffaelespazzoli do you know why scorecard is failing?

[aneeshkp]

@raffaelespazzoli alm-examples can't be empty
alm-examples: |
[]

[dmesser]

@raffaelespazzoli any update here?

[raffaelespazzoli]

@dmesser apologies, I am trying to figure out a way to automate creating the olm PR when I cut a new release of the operator. Any example there would help.

[raffaelespazzoli]

I created a new PR