Use warpgate.yaml for Container Healthcheck#1539
Merged
Eugeny merged 1 commit intowarp-tech:mainfrom Oct 21, 2025
Merged
Conversation
Member
|
Thank you! @all-contributors please add @micha-k for code |
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
2 participants
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 pull request implements a health check mechanism for the container using the warpgate.yaml configuration file. Without a specified path to the configuration, the health check currently looks for its settings under /etc/warpgate.yaml. However, if the config path is set as in all examples to /data, the container health status will always remain unhealthy. This change ensures that the health check correctly references the configuration, allowing for accurate health status reporting for the container.