-
Notifications
You must be signed in to change notification settings - Fork 14k
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
Add warning that liveness probe must be configured carefully #39930
Add warning that liveness probe must be configured carefully #39930
Conversation
content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
Outdated
Show resolved
Hide resolved
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
/label tide/merge-method-squash |
A common pattern for liveness probes is to use the same low-cost HTTP endpoint | ||
as for readiness probes, but with a higher `failureThreshold`. This ensures that the pod | ||
is observed as not-ready for some period of time before it is hard killed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should not be part of the caution?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tengqm Should I put this into 'note' section?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My feeling is that this can be in plain text. It is a hint, not something users must follow or must be alerted for.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright then I will modify the changes
45ffe06
to
994fa2c
Compare
/hold cancel |
Hello @tengqm I've modified the changes as you've asked...may you please review my changes. |
@KanishkaVerma054 thanks for the PR, it reads very well. I don't have anything to add as there are already great comments. |
/lgtm |
LGTM label has been added. Git tree hash: 73a65575e0be91bed70f9a4aeeab2bdb3e22ffed
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: binboum, tengqm The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…tes#39930) * a warning on liveness probes about cascading failures, added * A warning that liveness probe must be configured carefully. * better words are added * wrapping of the log lines * warning is modified that liveness probe must be configured carefully
…tes#39930) * a warning on liveness probes about cascading failures, added * A warning that liveness probe must be configured carefully. * better words are added * wrapping of the log lines * warning is modified that liveness probe must be configured carefully
Title of the Commit
Better words are used.
Which issue(s) this PR fixes
Part of #16607
Description
'killing' is replaced with 'restart' and 'pod' is replaced by 'container'.