jaeger-operator | Jaeger Operator for Kubernetes simplifies | Continuous Deployment library
kandi X-RAY | jaeger-operator Summary
kandi X-RAY | jaeger-operator Summary
The Jaeger Operator is an implementation of a Kubernetes Operator.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of jaeger-operator
jaeger-operator Key Features
jaeger-operator Examples and Code Snippets
Community Discussions
Trending Discussions on jaeger-operator
QUESTION
We have followed this tutorial to get mainflux up and running. After installing kubectl we added helm repos as follows
...ANSWER
Answered 2022-Jan-04 at 11:19In this case problem was the lack of the Ingressclass.
To solve this problem:
QUESTION
I am deploying Jaeger using the Jaeger Operator and it seems to be working fine. However, now I am trying to set up Prometheus metrics scraping (using the Prometheus Operator) but I am not seeing a Service
in my cluster that exposes the metrics ports for the Jaeger Collector (port 14269) or Query services (port 16687) (port number reference from the Jeager Monitoring documentation).
The only relevant Service
I see is jaeger-operator-metrics
:
ANSWER
Answered 2020-Nov-27 at 17:06I figured it out... the Jaeger Operator doesn't create a Service
exposing the metrics endpoints. These endpoints are just exposed via the pods for the Collector and Query components.
An example from the Collector pod spec:
QUESTION
I am using the Jaeger Operator to deploy the Jaeger Query and Collector services to Kubernetes (K3S actually) along with an ElasticSearch instance for the storage backend.
The Jaeger Operator creates an Ingress instance for the Jaeger Query service but it assumes that all of your Jaeger Agents will also be running inside the Kubernetes cluster. Unfortunately, that is not the case for me as some applications that I am tracing are not run within the cluster so I need my Jaeger Collector to be accessible from outside.
This Jaeger GitHub issue discusses a potential enhancement to the Jaeger Operator for this functionality and it suggests creating your own Ingress outside of the Operator to expose the Jaeger Collector but doesn't go into details.
I also want to utilize gRPC for the communication between the Agent outside the cluster and the Collector in the cluster and this article describes how to set up an Ingress for gRPC (though it is not specific to Jaeger). I used the example ingress spec there, made some tweaks for my scenario, and deployed it to my cluster:
...ANSWER
Answered 2020-Nov-23 at 14:58OK, I figured out the issue here which may be obvious to those with more expertise. The guide I linked to above that describes how to make an Ingress spec for gRPC is specific to NGINX. Meanwhile, I am using K3S which came out of the box with Traefik as the Ingress Controller. Therefore, the annotations I used in my Ingress spec had no affect:
QUESTION
Hi all I just created a fresh Kubernetes cluster and created a namespace called 'routing'
In here I created the latest traefik via the helm chart (2.2)
I can see the pod running fine.
No logs from the traefik pod.
When I run:
...ANSWER
Answered 2020-Aug-30 at 21:17Looks you need to expose port 9000
as the config comments say. Keep in mind the warning for production environments:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install jaeger-operator
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page