Skip to content
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

Problem with deployment in different namespace in the same cluster #86

Open
mteodor opened this issue Jul 28, 2021 · 0 comments
Open

Problem with deployment in different namespace in the same cluster #86

mteodor opened this issue Jul 28, 2021 · 0 comments

Comments

@mteodor
Copy link
Contributor

mteodor commented Jul 28, 2021

when trying to create additional deployment in the same cluster along with the existing one
one instance is installed as
helm install mainflux -n mf
when second instance is installed
helm install mainflux-prod -n mf-prod
installation is missing mainflux-jaeger-operator-jaeger Deployment (kubernetes resource), so pods are crashing with error

{"level":"error","message":"Failed to init Jaeger client: lookup mainflux-prod-jaeger-operator-jaeger-agent on 10.245.0.10:53: no such host","ts":"2021-07-28T09:10:36.719536418Z"}

maybe we should consider updating helm charts for jeager

additionally, dont know if that is the issue, when I tried to install with this command
helm install mainflux -n mf-prod
so same release name just different namespace I've got following error

W0727 16:54:35.902843  252425 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
Error: rendered manifests contain a resource that already exists. Unable to continue with install: PodSecurityPolicy "mainflux-jaeger-operator-operator-psp" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-namespace" must equal "mf-prod": current value is "mf"```

https://www.jaegertracing.io/docs/1.24/operator/

Installing the Operator
The Jaeger Operator can be installed in Kubernetes-based clusters and is able to watch for new Jaeger custom resources (CR)   in specific namespaces, or across the entire cluster. There is typically only one Jaeger Operator per cluster, but there might be at   most one Jaeger Operator per namespace in multi-tenant scenarios. When a new Jaeger CR is detected, an operator will  attempt to set itself as the owner of the resource, setting a label jaegertracing.io/operated-by to the new CR, with the operator’s  
 namespace and name as the label’s value.  
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ⛏ Backlog
Development

No branches or pull requests

1 participant