Update Jaeger upstream-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

[J0zi]

no labels, no tests, need to reopen

[jpkrohling]

Error from server (RequestEntityTooLarge): error when creating "/tmp/tmp.JJfeFF/deploy/jaeger.catalogsource.yaml": Request entity too large: limit is 3145728

Is this a new limit? This is probably related to:

• CRD generation not respecting "// +k8s:openapi-gen=false" operator-sdk#2285 (comment)
• make install fails with metadata.annotations too long .. kubernetes-sigs/kubebuilder#1140
• "jaegers.jaegertracing.io" is invalid: metadata.annotations: Too long jaegertracing/jaeger-operator#854
• Too long CRD definition jaegertracing/jaeger-operator#873

[jpkrohling]

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

[jpkrohling]

Removing WIP.

[jpkrohling]

The build seems to be failing due to:

Error from server (RequestEntityTooLarge): error when creating "/tmp/tmp.dPKpJp/deploy/jaeger.catalogsource.yaml": Request entity too large: limit is 3145728

@J0zi, is this something we should handle on our side, or is it a known issue?