Bug 1956644

Summary:	Liveness probe does not respect the next periodSeconds if timeoutSeconds over periodSeconds
Product:	OpenShift Container Platform	Reporter:	Kazuhisa Hara <kahara>
Component:	Node	Assignee:	Michael Burke <mburke>
Node sub component:	Kubelet	QA Contact:	MinLi <minmli>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	aos-bugs, mburke, mfojtik, minmli, rphillips, schoudha, xxia
Version:	4.6
Target Milestone:	---
Target Release:	4.8.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1954351	Environment:
Last Closed:	2021-05-14 12:40:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1954351
Bug Blocks:

Comment 2 Michael Burke 2021-05-05 15:30:09 UTC

Kazuhisa --

Does this rule apply to all health probes< Liveness, Readiness, and Startup? 

If so, can you please take a look at my PR? I added a note in multiple locations and added the default values for `periodseconds` and `timeoutSeconds` where appropriate.

https://github.com/openshift/openshift-docs/pull/32219

Thank you in advance.

Michael

Comment 5 Kazuhisa Hara 2021-05-06 03:54:50 UTC

Hello Michael,

Thank you for your effort.
I got same results to this summary with Readiness.
Therefore, I think the commit you wrote is correct and it looks great.

Thank you!
Kazuhisa

Comment 6 MinLi 2021-05-10 04:06:00 UTC

Hi, Michael

I comment on your pr, please take a look. Thanks

Comment 7 Michael Burke 2021-05-14 12:40:19 UTC

Changes are live: https://docs.openshift.com/container-platform/4.7/applications/application-health.html#odc-adding-health-checks