Issue with Consul Not Syncing Properly with Kubernetes

Hello everyone,

I’ve deployed Consul on an EKS cluster using a StatefulSet with 3 servers. When I deploy a microservice, Consul successfully registers it in its catalog. However, when I delete or update a deployment, Consul does not update its catalog. The old services remain visible on the Consul UI and are marked as “critical.”

How can I ensure that Consul properly syncs with Kubernetes so that services are deregistered or updated in Consul’s catalog when their corresponding Kubernetes deployments are deleted or modified?

Any advice or guidance would be greatly appreciated!

Thank you!

Is this for specific course or lab in that course? A link would be very useful here.

I’ve taken Kubernetes courses on the platform and wanted to try a concrete project, so I deployed several microservices on EKS and I’m using Consul for service discovery. However, my pods are not launching, and I’m seeing this error in the replicaset of the pod:

Error creating: Internal error occurred: failed calling webhook “consul-connect-injector.consul.hashicorp.com”: failed to call webhook: Post consul-connect-injector.consul.svc:443/mutate?timeout=10s : context deadline exceeded

My issue seems similar to this one: hashicorp/consul-helm#519.
Any help would be greatly appreciated!

I don’t think any of the support staff have much experience with Consul, TBH. You may want to try Hashicorp’s forums for help on this issue.