envoyproxy/envoy

TCP liveness checks through Envoy

Open

#7,783 opened on Jul 31, 2019

View on GitHub
 (10 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/tcp_proxyhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Is there a way for a service fronted by Envoy to be checked for liveness with a TCP connection? (Assuming the service cannot be reached directly without going through the proxy)

It seems that Envoy will accept any TCP connection, so the liveness check will always pass.

Envoy can set up active TCP checks for connection only as shown here. I would like that behavior but with an application on a different pod/node running the check.

Contributor guide

Research direction
Explore Envoy's health check configuration, particularly the TCP health check settings. Look into the possibility of using active health checks with a custom endpoint or using Envoy's admin endpoint for health checks. Also consider using a sidecar or separate health check service.
Tech stack
cpp
Domain
backendinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Envoynetwork health checks
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50