-
-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Telepresence with Consul #3232
Comments
Telepresence might collide with Consul because it too uses an Envoy sidecar. Here are some things you can try: Use different values for the Envoy ports. Create a yaml file and use agent:
envoy:
serverPort: 18100
adminPort: 19100 Also, to make sure that the Telepresence pod injection sees the Consul injection, try adding: agentInjector:
webhook:
reinvocationPolicy: IfNeeded Look at the created pod to determine how Telepresence and Consul injected containers are configured, e.g. |
Hello, Thank you. I've tried this but I am still unable to route traffic to my local machine for a deployed spring boot service. Below is a screenshot of the traffic manager configuration When I run telepresence list, it shows that my service is being intercepted And this is my pod where the traffic agent was installed: When I intercept my service, it remains accessible even if I don't run it locally so it seems like Intercept is not re-routing the traffic. I tried telepresence locally with minikube and it worked fine. However, on my dev cluster where I have a gateway service and consul, it does not work. Finally, my pod config yaml file: |
Hi @eliesemaan6 , can you share your intercept command? We’d like to check which port you’re using there - perhaps there’s an issue with using a numeric target port for your service with a service mesh. Also could you share your Service configuration and is your Service using a numeric or symbolic target port? |
Hello Cindy, This is my intercept command: telepresence intercept mxenv-definition-service --port 8085:http --env-file D:\telepresence\mxenv-definition\mxenv-definition.env --workload mxenv-definition-deployment And below is my service config: |
Thanks for that. What version of Consul are you using? |
I am facing the exact issue. My consul for Kubernetes version 1.16.x Thanks! Updated: I can confirm that if I hit via curl: curl 10.168.X.Y:9900/api/abc/v1/version, it will hit my local service running on my MAC. I am not sure if telepresence with latest version 2.15.1 supports API Gateway, especially the consul API Gateway/Mesh. |
@kha7281 , if you run |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment, or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
Describe the bug
I have Consul installed in my cluster for service discovery. I am trying to intercept a service with telepresence.
Issue is similar to #2426
The traffic agent is added to the POD but nothing gets intercepted.
The suggestion on that issue was to use a newer version, however I am using Telepresence 2.13.3 and I have the same behavior. Is telepresence intercept supported with Consul?
Thank you
The text was updated successfully, but these errors were encountered: