Configure Liveness, Readiness and Startup Probes

kubernetes / website

Kubernetes website and documentation repo:

https://kubernetes.io

Creative Commons Attribution 4.0 International

4.38k stars 14.14k forks source link

Configure Liveness, Readiness and Startup Probes #45081

Open pinakig22 opened 5 months ago

pinakig22 commented 5 months ago

The failureThreshold in section Configure Probes is missing the threshold value, i.e. 3, which is the default as checked from pod yaml output when not defined in pod definition file.

failureThreshold: After a probe fails failureThreshold times in a row --> failureThreshold: After a probe fails failureThreshold 3 times in a row

Example of pod yaml output

k8s-ci-robot commented 5 months ago

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

utkarsh-singh1 commented 5 months ago

/language en

utkarsh-singh1 commented 5 months ago

Default value : 3 can be mentioned in the bracket.

k8s-triage-robot commented 2 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

tengqm commented 2 months ago

This has to be fixed in the upstream source code. We can, however, mention the default value when articulating the concepts.

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

utkarsh-singh1 commented 1 month ago

/remove-lifecycle rotten

utkarsh-singh1 commented 1 month ago

@pinakig22, As above already mentioned there can be any value of failureThreshold in PodSpec, so it would be better to keep mention failureThreshold as it is.

utkarsh-singh1 commented 1 month ago

Screenshot_20240610_233649

utkarsh-singh1 commented 1 month ago

Default value : 3 can be mentioned in the bracket.

It can be mentioned here.