Update Jaeger community-operators to v1.17.0

[jpkrohling]

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

• Has you operator 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 a PR against this repo and explain your need

² For more information see here

[jpkrohling]

cc @objectiser

[jpkrohling]

CVP/operator-olm-deployment

Is this check failure expected, or is there something wrong with our CSV?

[J0zi]

/test CVP

[jpkrohling]

Marking this as WIP, as I found a problem with this CSV, related to jaegertracing/jaeger-operator#931

[jpkrohling]

Removing WIP.

[J0zi]

/test CVP

[jpkrohling]

@J0zi, can we get the logs for the check that failed? All I can see is this:

Failed to deploy the operator with OLM: java.lang.Exception: Error running Ansible playbook 'deploy-olm-operator.yml': hudson.AbortException: script returned exit code 2

[J0zi]

I will give it another chance, we will see. Waiting for a result.

[J0zi]

/test CVP

[J0zi]

investigating

[J0zi]

@jpkrohling, it failed on the following:
TASK [deploy_olm_operator : Push the operator metadata to the private quay.io repository]

[jpkrohling]

What does that mean? Is there something I have to fix in the CSV? During my manual tests, I was able to push this to my private quay.io repository and create an operator-source from it, and a subscription afterwards.

[gallettilance]

@jpkrohling @J0zi can you double check that your validation schema is correct? That crd is very large and it seems to contain a lot of duplicate fields. Can you confirm that this file is correct?

[J0zi]

still investigating
ERROR:operatorcourier.push: 413 Request Entity Too Large
@jpkrohling, CRD has 21000 lines.

[jpkrohling]

As part of jaegertracing/jaeger-operator#932 , we have recently removed the descriptions from the CRD, making it far smaller. I added another commit to this PR to use that CRD instead.

A similar PR to this one has been merged already, adding the Jaeger 1.17.0 CSV to the upstream community operators. To bring a similar change to that, I also created #1299, but this might be a sign that the tests between community operators and upstream community operators should be aligned.

[J0zi]

Hi @jpkrohling, currently, catalog-initialization fails on following:
fatal - error loading manifests from directory: error checking provided apis in bundle : couldn't find jaegertracing.io/v1/Jaeger (jaegers) in bundle. found: map[]"

[jpkrohling]

Looks like it's now passing!

[J0zi]

@jpkrohling please squash your commits. And consider similar updates to #1299.

[jpkrohling]

And consider similar updates to #1299.

It is already in sync with this PR here.

[J0zi]

/test CVP