hashicorp / hashicorp/consul

sidecar health check fail

Open
#11,008 8 comments 0 reactions 0 assignees View on GitHub
type/question
Dominant language
Go
Stars
30.1k
Forks
4.6k
Avg merge
1d 18h
Merged PRs (30d)
39

Description

consul version :1.10.1
envoy version:1.18.3

whe use[ Sidecar Service Registration](https://www.consul.io/docs/connect/registration/sidecar-service)

```json
{
"Connect": {
"SidecarService": {
"Proxy": {
"Upstreams": [
{
"DestinationName": "server",
"LocalBindPort": 1234
}
]
}
}
},
"ID": "client-82",
"Name": "client",
"Tags": [],
"Address": "10.19.128.111",
"Meta": {
"secure": "false"
},
"Port": 82,
"Check": {
"Interval": "10s",
"HTTP": "http://10.19.128.111:82/actuator/health",
"Header": {}
}
}
```

the sidecar health check will fail because " dial tcp 127.0.0.1:21001: connect: connection refused"。

Check the Envoy 21001 port I find it bind on machine ip(10.19.128.111) but not 127.0.0.1。

How to make Envoy bind on 127.0.0.1 ?

Contributor guide

Open the contributing guide

Research direction

Start with the Sidecar Service Registration documentation and the supplied Consul 1.10.1 and Envoy 1.18.3 configuration. Reproduce the failing health check, then inspect the address exposed for Envoy port 21001 versus the configured machine address. Done means the sidecar health check succeeds and the listener behavior is documented or corrected.

Written by the indexing model from the issue text.

Assessment

Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.