hansehe/jaeger-all-in-one

Jaeger tracing all-in-one service for development purposes

Jaeger Tracing - All In One

The Jaeger tracing all-in-one service enables jaeger for development purposes, check out:

• https://www.jaegertracing.io/docs/1.55/getting-started/

Run With Docker

docker-compose -f docker-compose.yml up

Access jaeger at:

• http://localhost:16686/

Access hotrod tracing demo at:

• http://localhost:8080/

Use Helm Repo

helm repo add jaeger-all-in-one https://raw.githubusercontent.com/hansehe/jaeger-all-in-one/master/helm/charts
helm repo update

helm install jaeger-all-in-one jaeger-all-in-one/jaeger-all-in-one

jaeger-all-in-one's Issues

Metadata kubernetes version passing as number values instead of string value

Hello,

When I tried to use your helm chart it's failing because of metadat has kubernetes version which is bieng getting as number which is not acceptable in kubernetes manifest.

Could you please create a fix for the same or provide solutions to use it.

Liveness & Readiness probe configuration

Jaeger deployment fails due to default liveness & readiness probe values especially in an environment with limited resources or slow machine types. It would be good to have configurable liveness and readiness probe settings.

Support for newer kubernetes versions

I tested your helm with current minikube and k8s and cant install chart.

Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: resource mapping not found for name: "jaeger-all-in-one" namespace: "default" from "": no matches for kind "Ingress" in version "networking.k8s.io/v1beta1" ensure CRDs are installed first

So ingress template should be changed to use "networking.k8s.io/v1" for higher kubernetes versions.

minikube version
# minikube version: v1.26.0

kubectl get node
# NAME       STATUS   ROLES           AGE   VERSION
# minikube   Ready    control-plane   12d   v1.24.1

Prometheus configuration

Hi,

I have installed 1.47 all in one, but i am not able to see data in Monitor tab. is prometheus needs to be install separately?

OTLP Ports

@hansehe Can you please add OTLP ports (4317 and 4318) in the configuration of https://github.com/hansehe/jaeger-all-in-one/blob/master/helm/jaeger-all-in-one/templates/service.yaml and release a new version?

jaegertracing/all-in-one container drains memory to the point the hosting system crashes

I've set up recently a system and added jaegertracing/all-in-one container too.
Initially I've noticed that my hosting system which is a dual CPU Xeon 2630 V2 with 64GB of RAM was dying after 2-3 hours of intensive load. I thought that my app could be at fault, but after investigating a bit I noticed that the problem is actually jaegertracing/all-in-one container container which is slowly consuming all the system available RAM memory until the system crashes.
It looks like a memory leak to me.
The only way to stabilize my system was to remove the jaegertracing/all-in-one container

My system containers are all running on a docker instance.

docker-compose section for jaegertracing looks like below. I haven't defined any memory limits on this container, so I cannot tell you if that trick would have reduce the leak or not.

  jaeger-all-in-one:
    image: jaegertracing/all-in-one:latest
    restart: always
    ports:
      - "16686:16686"
      - "14268"
      - "14250"
    networks:
      mw-network:
        aliases:
          - jaeger-all-in-one