-
Notifications
You must be signed in to change notification settings - Fork 556
docker: add default healthcheck to container images #4161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
docker: add default healthcheck to container images #4161
Conversation
Adds HEALTHCHECK instruction using `cscli lapi status` to verify the local API is responding. Related to crowdsecurity#4160 Related to crowdsecurity#3603
|
@LaurenceJJones: There are no 'kind' label on this PR. You need a 'kind' label to generate the release automatically.
DetailsI am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository. |
|
@LaurenceJJones: There are no area labels on this PR. You can add as many areas as you see fit.
DetailsI am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4161 +/- ##
=======================================
Coverage 62.94% 62.94%
=======================================
Files 467 467
Lines 33298 33298
=======================================
Hits 20961 20961
- Misses 10218 10220 +2
+ Partials 2119 2117 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Just thought if LAPI only container then what? Need to test |
|
what if it's a log processor only? it will test the health of the LAPI container, not the LP. |
Well it will test the health between lp and lapi so technically not bad, but we don't really have a way to know I'm healthy for lp only. |
maybe metrics? log processors still expose them when lapi is disabled, and they shouldn't kick in unless LP is healthy. I'm not saying we should do that, just that they are available. |
Adds HEALTHCHECK instruction using
cscli lapi statusto verify the local API is responding.Related to #4160
Related to #3603