feat: implement healthcheck start_interval #3226
Open
+34
−1
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
Signed-off-by: Khushiyant <khushiyant2002@gmail.com>
Signed-off-by: Khushiyant <khushiyant2002@gmail.com>
Khushiyant
force-pushed
the
healthcheck-start
branch
from
8a9d8f0
to
e6fbfae
Compare
Khushiyant
changed the title
Khushiyant
changed the title
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.
Closes #3157
Added support for
StartIntervalasPOST /containers/createnow accepts aHealthConfig.StartIntervalto set theinterval for health checks during the start period. This extends the interval that health checks can use during the initial phase. Usually, you want to verify that a container is ready sooner rather than later than when it is just getting started.
It was introduced as part of v1.44 API changes