-
Notifications
You must be signed in to change notification settings - Fork 9.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add
insecure-health-endpoint
flag to enable Kubernetes HTTP probes
Before this patch, Kubernetes users deploying etcd who configure mTLS authentication for client and metrics endpoints are unable to leverage etcd's `/health` endpoint for liveness or readiness probes because Kubernetes HTTP probes don't support mTLS. Users must work around this limitation with strategies like weak health checks using custom `exec` probes. Bypassing the `/health` endpoint for this purpose can lead to false positive probe results and quorum loss if a member is falsely determined to be ready during a rollout. This patch introduces an `--insecure-health-endpoint` flag which, if specified, enables an insecure HTTP `/health` endpoint which is functionally equivalent to other `/health` endpoints. This enables etcd pods to specify reliable HTTP GET probes for readiness and liveness checking. This approach stands as an alternative to introducing a parallel TLS configuration and listener just for the `/health` endpoint. The typical use case is probably a non-exposed port used only by a container orchestration component (e.g. the Kubelet). Fixes #11993.
- Loading branch information
1 parent
0aab02e
commit a4ded77
Showing
9 changed files
with
102 additions
and
21 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters