New channel due to missing replaces

[J0zi]

Hi @pb82,

we added a version to separate channel as it actually fall off the update graph and are orphaned and not installable / upgradable anymore due to missing replaces in the path. After this PR, it will be installable from this channel.
The main reason for this update is that we are currently preparing to enable bundle based catalogs which involves background conversion, it’s currently failing for the reason stated above. Please approve with /lgtm.

Signed-off-by: j0zi [email protected]

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.

---

New Submissions

• 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?

Updates to existing Operators

• Is your new CSV pointing to the previous version with the replaces property?
• 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?

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 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 an issue against this repo and explain your need

² For more information see here

[pb82]

@J0zi the missing replace was intentional as there is no automatic upgrade path from 2.x.x to 3.x.x. Is there a better way to handle such scenarios?

[pb82]

/lgtm

[openshift-ci-robot]

@pb82: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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]

@pb82 When there is no replaces or skips instructions these things fall out of the update graph completely. This is because that graph is constructed by looking at what's latest in a channel and then walk back via these pointers. If nothing points anymore to your 2.x.x version the graph ends at the earliest 3.x.x release. While this could be intentional it is also disruptive for users. We have ways around that by serving 2.x.x in a separate channel.