You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
from the above example, the path '/static' and '/search' are very common path. if the 2 applications have the same path, we cannot expose them by the same ingress controller. kiali is using 'static' while jaeger is using 'static' as well.
If the application have the contextpath, then we can use the following way to achieve this goal. Take 'jaeger' as an example to explain:
you can configure jaeger-query to run at a custom prefix, like /jaeger
$ go run ./cmd/query/main.go help| grep base-path
--query.base-path string The base path for all HTTP routes, e.g. /jaeger; useful when running behind a reverse proxy (default "/")
I have a case to integrate some ui together and expose them by using the same ingress controller. here is an example ingress file:
from the above example, the path '/static' and '/search' are very common path. if the 2 applications have the same path, we cannot expose them by the same ingress controller. kiali is using 'static' while jaeger is using 'static' as well.
If the application have the contextpath, then we can use the following way to achieve this goal. Take 'jaeger' as an example to explain:
so we should have a contextpath for the application. for jaeger application, can we consider to have a contextpath? Thanks.
The text was updated successfully, but these errors were encountered: