Enhance Service Dependency with Healthcheck Condition #48
Conversation
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
|
Sure, thanks! 🚀 |
Add Healthcheck Condition to Tailscale Dependencies
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.
Suggestion:
Add condition: 'service_healthy' to 'depends_on'.
Previously, the 'depends_on' configuration did not include the 'condition: service_healthy' for the Tailscale container. With the recent update improving the Tailscale container's healthcheck, this addition ensures the dependent service waits for Tailscale to be fully operational before starting. This change improves the reliability and stability of the service dependency chain.
I'd be happy to add this to every service in the repo should you like me to?
Cheers, Adam