Replies: 1 comment
-
Hello, @Cuwudia! I'm here to help you with your Jaeger UI configuration. Let's tackle this issue together. To configure the Jaeger UI with path-based routing and avoid the 500 error from your Nginx ingress controller, you need to adjust your Ingress resource. Here is an example configuration that should work for your setup: apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
labels:
app: jaeger
app.kubernetes.io/component: query-ingress
app.kubernetes.io/instance: simplest
app.kubernetes.io/managed-by: jaeger-operator
app.kubernetes.io/name: simplest-query
app.kubernetes.io/part-of: jaeger
name: simplest-query
namespace: observability
annotations:
kubernetes.io/ingress.class: nginx
nginx.ingress.kubernetes.io/add-base-url: "true"
nginx.ingress.kubernetes.io/from-to-www-redirect: "true"
nginx.ingress.kubernetes.io/rewrite-target: /$2
nginx.ingress.kubernetes.io/ssl-redirect: "true"
nginx.ingress.kubernetes.io/use-regex: "true"
nginx.ingress.kubernetes.io/enable-compression: "true"
spec:
ingressClassName: nginx
tls:
- hosts:
- <obfuscated>
secretName: ingress-tls
rules:
- host: <obfuscated>
http:
paths:
- path: /jaeger(/|$)(.*)
pathType: Prefix
backend:
service:
name: simplest-query
port:
number: 16686 Key changes:
This configuration should help you access the Jaeger UI at |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello I have trouble accessing the jaeger UI though my ingress controller. The issue is that domain/ is taken already so i have to use domain/jaeger. however im getting 500 from my nginx controller. If i port forward the service i dont have issue however that is not a viable long term solution.
here is my ingress resource :
Beta Was this translation helpful? Give feedback.
All reactions