docs(deployment): add liveness and readiness probes to Kubernetes manifest#215
Open
andrerfneves wants to merge 1 commit into
Open
docs(deployment): add liveness and readiness probes to Kubernetes manifest#215andrerfneves wants to merge 1 commit into
andrerfneves wants to merge 1 commit into
Conversation
…ifest Add HTTP health probes to the Kubernetes Deployment example so that Kubernetes can properly manage container lifecycle and traffic routing. - livenessProbe: HTTP GET / on port 80, starts after 10s, checks every 30s - readinessProbe: HTTP GET / on port 80, starts after 5s, checks every 10s Without these probes, Kubernetes cannot detect when the nginx container is unhealthy or not ready to serve traffic.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds HTTP health probes (liveness and readiness) to the Kubernetes Deployment example in
DEPLOYMENT_DOCKER.md.Why
The Kubernetes manifest was missing health probes, which are essential for production deployments:
The probes use the existing nginx health endpoint (
HTTP GET /on port 80), which requires no additional dependencies since nginx responds with 200 on the root path by default.Changes
DEPLOYMENT_DOCKER.md: AddedlivenessProbeandreadinessProbeto the container spec in the Kubernetes manifest:Test Plan