[stable/jaeger-operator] Chart needs updating to use RoleBinding instead of ClusteRoleBinding

[danielmbarlow]

Describe the bug
Using the chart you can't get spans from applications that have had the sidecar agent injected if they are in a different namespace to the Jaeger deployment.

Version of Helm and Kubernetes:
Helm:

Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}

Kubernetes:

Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.7-gke.8", GitCommit:"7d3d6f113e933ed1b44b78dff4baf649258415e5", GitTreeState:"clean", BuildDate:"2019-06-19T16:37:16Z", GoVersion:"go1.11.5b4", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
stable/jaeger-operator

What happened:
A Jaeger instance in one namespace doesn't pick up traces from applications in other namespaces with sidecar injected.

What you expected to happen:
I expected the fix for that issue to have been picked up from the jaeger-operator repository.

How to reproduce it (as minimally and precisely as possible):
Works:

• Installed the chart in the default Kubernetes namespace using Helm
• Create a Jaeger instance in the default namespace
• Create a deployment in the default namespace, with the sidecar agent injected
• Create spans. They appear in Jaeger

Works:

• Install the operator without Helm using the commands specified in the operator in the observability namespace
• Create a deployment with Sidecar injected in the default namespace
• Create spans. They appear in Jaeger

Doesn't work:

• Installed the chart in the jaeger Kubernetes namespace using Helm
• Create a Jaeger instance in the jaeger namespace
• Create a deployment in the default namespace, with the sidecar agent injected
• Create spans. They don't appear in Jaeger.

Anything else we need to know:
This discussion shows that other developers have faced the same issue I believe and worked around it using raw template files.

[danielmbarlow]

This issue fixed in version 2.9.0 of the chart (#14629)
Thanks @alexsn & @cpanato
If you faced this issue you may need to redeploy apps and the Jaeger instance after updating the Jaeger Operator deployment so Sidecar Agents can send data to the newly created Jaeger instance.