Open stanworld opened 1 year ago
This is like a follow up for the host support at issue:
Thanks for creating the issue. Would you like to send a PR? @stanworld
@iblancasa , I love to help but frankly I am quite new to this, and not sure where to get started. If someone can give some suggestions, I'd give a try.
@stanworld awesome!
pkg/ingress/query.go
to see how Ingress objects are createdJaeger.Spec.Query.Options
similar to query.base-path
for your missing fields. Or maybe, it can be a new field in Jaeger.Spec.Ingress.Options`.I think the issue is not within the ingress creation piece but how jaeger operator handles an ingress with a path. The template posted in the problem will actually create an ingress like mydomain.com/jaeger, but it seems js/css doesn't know how to handle it.
@stanworld Is it a behavior you can reproduce without the operator? Because, in that case, it would make more sense to open an issue in the Jaeger repo
Requirement
We have a domain name used for our applications in a cluster (mydomain.com), and would like to add jaeger support at mydomain.com/jaeger
Problem
When I try to create a ingress backed up jaeger-query service like:
apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: my-jaeger spec: ingressClassName: nginx rules:
Refused to apply style from 'http://mydomain.com:9080/static/index-c3b54a40.css' because its MIME type ('text/plain') is not a supported stylesheet MIME type, and strict MIME checking is enabled. jaeger:41 GET http://mydomain.com:9080/static/index-5a1abd6a.js net::ERR_ABORTED 401 (Unauthorized)
Proposal
No response
Open questions
No response