nginx inc ingress controller telemetry - 404 Not Found #6740
Replies: 1 comment
-
duplicate of #6741 |
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
-
i am using nginx inc ingress controller in openhift. i configured otlp and telemetry ingress controller ymal as below
otlp:
kind: Ingress
apiVersion: networking.k8s.io/v1
metadata:
name: otlp
namespace: istio-system
annotations:
ingress.kubernetes.io/ssl-redirect: 'false'
kubernetes.io/ingress.class: nginx
nginx.org/basic-auth-realm: Authentication Required - otlp
nginx.org/basic-auth-secret: basic-auth-secret
spec:
tls:
secretName: xxx
rules:
http:
paths:
pathType: Prefix
backend:
service:
name: jaeger-collector
port:
number: 4318
zipkin:
kind: Ingress
apiVersion: networking.k8s.io/v1
metadata:
name: zipkin
namespace: istio-system
annotations:
ingress.kubernetes.io/ssl-redirect: 'false'
kubernetes.io/ingress.class: nginx
nginx.org/basic-auth-realm: Authentication Required - zipkin
nginx.org/basic-auth-secret: basic-auth-secret
nginx.org/rewrites: serviceName=jaeger-collector rewrite=/$1
spec:
tls:
secretName: xxx
rules:
http:
paths:
pathType: Prefix
backend:
service:
name: jaeger-collector
port:
number: 9411
otlp request worked correctly. But when i request telemetry addresses "https://xxx/api/v2/spans" return 404 Not Found. How can i fix this?
Nginx Ingress Operator version:
2.3.2 provided by NGINX Inc
actually path is in zippin like this:
Beta Was this translation helpful? Give feedback.
All reactions