BC-8811 - Reconfigure the Probs for etherpad #1092
Merged
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.
Description
Set the initialeDelaySeconds for the readinessProbe and livenessProb to 0 so that is hase not effect and Ansible over wirte it.
Add an startupProbe to the Etherpad deployment so that every 5 seconds for an Failuer Thrashold von 60 will be show if Etherpad is up and runing. So we detect the Earlys timepoint where the user cann access the POD via HTTP.
We hatte seen at Production that an initial delay off 60 seconds where to low in some cases and we nead an delay like 120 seconds or 180 seconds on wone hand but on the other hand we hade ssen Etherpad PODs who where up in like 30 seconds.
This Problem had shown that it's easer to add an startupProbe who test it every 5 Seconds for an failure threashod of 60 woud be better, so if the POD is up after 30 second the failure count is at 6 and if the POD is up after 90 seconds the failure count is up to 9.
Links to Tickets or other pull requests
Changes
Datasecurity
Deployment
New Repos, NPM pakages or vendor scripts
Screenshots of UI changes
Approval for review