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
To test Consul service mesh in "Transparent Proxy" mode, We deployed in a AWS EKS "static-server" (hashicorp/http-echo) and "static-client" (curlimages/curl) images in the service mesh (sidecar proxy injection: connectInject / consul dataplane), as sample code on consul documentation do.
NOTE: we use AWS EC2 SPOT instances in sandboxing/texting environments
Calls from static-client to static-server (curl), works fine using proxy and using these FQDN:
static-server.service.consul (consul dns resolve to a static-server Pod IP)
static-server.connect.consul (consul dns resolve to a static-server Pod IP)
static-server.virtual.consul (consul dns resolve to 240.x.x.x - private virtual IP used by sidecar proxy)
After some hours we cannot anymore get a correct response from static-server using these FQDN:
(KO) static-server.service.consul
(KO) static-server.connect.consul
But no issue for the FQDN:
(OK) static-server.virtual.consul
A restart for static-server deployment resolve the issue.
Reproduction Steps
Steps to reproduce this issue:
Deploy consul on AWS EKS cluster/datacenter with ArgoCD
Deploy static-server and static-client in different specific namespaces enabling connectInjection (Transparent Proxy enable by default in chart)
Set WAN Federation with Mesh Gateway with other consul clusters/datacenter
Run commands like kubectl -n static-client exec deploy/static-client -c static-client -- curl http://static-server.service.consul
Get correct responses from static-server (for all three FQDNs)
Overview of the Issue
To test Consul service mesh in "Transparent Proxy" mode, We deployed in a AWS EKS "static-server" (hashicorp/http-echo) and "static-client" (curlimages/curl) images in the service mesh (sidecar proxy injection: connectInject / consul dataplane), as sample code on consul documentation do.
NOTE: we use AWS EC2 SPOT instances in sandboxing/texting environments
Calls from static-client to static-server (curl), works fine using proxy and using these FQDN:
After some hours we cannot anymore get a correct response from static-server using these FQDN:
But no issue for the FQDN:
A restart for static-server deployment resolve the issue.
Reproduction Steps
Steps to reproduce this issue:
kubectl -n static-client exec deploy/static-client -c static-client -- curl http://static-server.service.consul
kubectl -n static-client exec deploy/static-client -c static-client -- curl http://static-server.service.consul
Consul info for both Client and Server
Client info
Server info
Operating system and Environment details
AWS EKS Cluster
Client Version: v1.29.0-eks-5e0fdde
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.12-eks-2d5f260
Log Fragments
The text was updated successfully, but these errors were encountered: