Add liveness / readiness check to ddp-streamer #202
Merged
+23
−0
Conversation
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
gabrielpetry
approved these changes
Oct 16, 2025
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.
This adds health check probes and exposes a new HTTP port in the
microservices-ddp-streamer-deployment.yamltemplate to improve container monitoring and readiness. These changes help Kubernetes better manage the service lifecycle and ensure the application is running and ready to serve traffic.Container health and readiness improvements:
http, port 3000) to the container's ports list for health checks and service access.livenessProbeand areadinessProbethat use HTTP GET requests to the/healthendpoint on the new HTTP port, enabling Kubernetes to monitor the container's health and readiness state.