jaeger-operator | Jaeger Operator for Kubernetes simplifies | Continuous Deployment library

by jaegertracing Go Version: v1.45.0 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | jaeger-operator Summary

jaeger-operator is a Go library typically used in Devops, Continuous Deployment applications. jaeger-operator has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

The Jaeger Operator is an implementation of a Kubernetes Operator.

Support

Quality

Security

License

Reuse

Support

jaeger-operator has a medium active ecosystem.

It has 923 star(s) with 318 fork(s). There are 17 watchers for this library.

There were 1 major release(s) in the last 12 months.

There are 121 open issues and 738 have been closed. On average issues are closed in 242 days. There are 12 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of jaeger-operator is v1.45.0

Quality

jaeger-operator has 0 bugs and 0 code smells.

Security

jaeger-operator has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

jaeger-operator code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

jaeger-operator is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

jaeger-operator releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 25050 lines of code, 1186 functions and 220 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of jaeger-operator

Get all kandi verified functions for this library.

jaeger-operator Key Features

No Key Features are available at this moment for jaeger-operator.

jaeger-operator Examples and Code Snippets

No Code Snippets are available at this moment for jaeger-operator.

Community Discussions

Trending Discussions on jaeger-operator

Mainflux on Kubernetes with ingress-nginx

Do metrics published by the Jaeger Operator include those from the Collector and Query services too?

Expose Jaeger Collector to clients outside of cluster

Traefik Helm Chart 404

QUESTION

Mainflux on Kubernetes with ingress-nginx

Asked 2022-Jan-04 at 11:19

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:19

In this case problem was the lack of the Ingressclass.

To solve this problem:

Source https://stackoverflow.com/questions/70530418

QUESTION

Do metrics published by the Jaeger Operator include those from the Collector and Query services too?

Asked 2020-Nov-27 at 17:06

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:06

I 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:

Source https://stackoverflow.com/questions/65040519

QUESTION

Expose Jaeger Collector to clients outside of cluster

Asked 2020-Nov-23 at 14:58

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:58

OK, 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:

Source https://stackoverflow.com/questions/64938228

QUESTION

Traefik Helm Chart 404

Asked 2020-Aug-30 at 21:17

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:17

Looks you need to expose port 9000 as the config comments say. Keep in mind the warning for production environments:

Source https://stackoverflow.com/questions/63658154

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install jaeger-operator

Firstly, ensure an ingress-controller is deployed. When using minikube, you can use the ingress add-on: minikube start --addons=ingress. Then follow the Jaeger Operator installation instructions.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: