-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to: create Jaeger instance in different namespace to operator #24
Comments
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. |
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 |
@dylanfoster I think this is because the operator watches only a single namespace: jaeger-operator/pkg/cmd/start/main.go Line 84 in 1e134be
If you are comfortable with Go, could you try removing the mgr, err := manager.New(cfg, manager.Options{}) According to the manager's documentation, an empty |
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.
The text was updated successfully, but these errors were encountered: