Replies: 1 comment 2 replies
-
Hi @ndtai772! Unfortunately, inbound traffic into the kong ingress controller via the public domain is HTTPS which means that the Linkerd proxy can't decrypt it and apply service profiles. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Due to some reasons, I couldn't use the Linkerd proxy in Ingress mode for Ingress controllers. I tried to set up an external service profile for a service using the host header (domain name in case of ingress controller), but the config didn't seem to work well.
Currently, I have:
echo-kong-server.lab
) which have Linkerd proxy meshed tooI tried to enable external-service-profiles on both the ingress controller & the pod, but still, there weren't any
route_.*
metrics.The response from the echo server:
Is it possible to get Per-route metrics from ingress traffic without using the Linkerd proxy in Ingress mode?
Beta Was this translation helpful? Give feedback.
All reactions