Gleb Kragel

no, i would ask for someone who knows how to run and up jaeger-operator in not cluster-wide mode to complete documentation. I have already spent three days to run jaeger...

I also try creat role in myproject namespace which solve log errors like in this: `time="2022-05-19T19:31:37Z" level=error msg="error getting a list of deployments to analyze in namespace" error="deployments.apps is forbidden:...

I think it's impossible to start jaeger-operator in not cluster-wide mode when follow steps in documention. Could your team can test it and give response about statement above?

@yurishkuro hello. Will anyone help solve it?

no one help

Steps (use minikube): 1) install cert-manager v1.6.3 (follow [this](https://cert-manager.io/v1.6-docs/installation/kubectl/#steps) guide) 2) download [jaeger-operator](https://github.com/jaegertracing/jaeger-operator/releases/download/v1.34.0/jaeger-operator.yaml) manifest (from [documentation](https://www.jaegertracing.io/docs/1.34/operator/#installing-the-operator-on-kubernetes)) 3) as documentation told if i want to install jaeger-operator in non cluster wide...

@rubenvp8510 can you try to install jaeger-operator in mode, when look for jaeger CR in not observability namespace

apply manifest from your post above and see in log that jaeger-operator run in not cluster wide mode.  pod of jaeger operator also has restarts   

About log ok, i undestand. Wait for your answer Check your manifest. Pod of jaeger operator restarting. I tried to deploy operator used your manifest

Great, we have found issue. Yhanks for your work. I will look forward to closing PR. what about that question? 4. create [this](https://github.com/tide34/jaeger-operator/blob/main/additional.yaml) manifest in namespace app-profile (documentation [link](https://www.jaegertracing.io/docs/1.34/operator/#install-modes). I...