Bug 2034361: rgw: add startup probe to RGW pod #320
Conversation
Add a startup probe to the RGW pod. Allow 180 seconds for the RGW to start responding to its /swift/healthcheck endpoint. Usually the RGW starts up in less than 30 seconds, but it has observed to start between 60-90 seconds into container start in some instances. Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: BlaineEXE The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| }, | ||
| InitialDelaySeconds: 10, | ||
| PeriodSeconds: 10, | ||
| FailureThreshold: 18, |
There was a problem hiding this comment.
So the total threshold time is 180s? And if it still didn't pass the probe the pod will be restarted, right?
BlaineEXE
changed the title
travisn
changed the title
|
@BlaineEXE: Bugzilla bug 2034361 is in an unrecognized state (MODIFIED) and will not be moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Add a startup probe to the RGW pod. Allow 180 seconds for the RGW to
start responding to its /swift/healthcheck endpoint. Usually the RGW
starts up in less than 30 seconds, but it has observed to start between
60-90 seconds into container start in some instances.
Signed-off-by: Blaine Gardner blaine.gardner@redhat.com
Description of your changes:
Which issue is resolved by this Pull Request:
Resolves #
Checklist:
make codegen) has been run to update object specifications, if necessary.