How to: create Jaeger instance in different namespace to operator

[objectiser]

One of the benefits of the operator is supposed to be that it can be installed once, and used to create multiple Jaeger instances in different namespaces.

If this is possible, then we should document (possibly just in the readme) how such a configuration would be achieved.

[containerpope]

This would be very beneficial because the actual deployment model would say one Jaeger Operator per Namespace and if you install by Helm, the installation fails after the second one, because the CRD is already existing.

[dylanfoster]

Trying this as well, with the operator in the default namespace, it "creates" the jaeger instance in another namespace but the pods never show up, nor do the agent sidecars

[jpkrohling]

@dylanfoster I think this is because the operator watches only a single namespace:

jaeger-operator/pkg/cmd/start/main.go

Line 84 in 1e134be

mgr, err := manager.New(cfg, manager.Options{Namespace: namespace})

If you are comfortable with Go, could you try removing the Namespace part? Like this:

	mgr, err := manager.New(cfg, manager.Options{})

According to the manager's documentation, an empty Namespace would default to watching all namespaces:

https://github.com/kubernetes-sigs/controller-runtime/blob/0dd6edb02bf23e3669a3edc50ef00a38719173b0/pkg/manager/manager.go#L111-L115