Skip to content

Commit 18e0db6

Browse files
committed
Document health probes config property in Actuator section
This commit mentions the `management.health.probes.enabled` configuration property in the Kubernetes Probes section of the Actuator chapter. Enabling this property is required if we need to expose Kubernetes Probes in a non-Kubernetes environment. Fixes gh-21505
1 parent a12a305 commit 18e0db6

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

spring-boot-project/spring-boot-docs/src/docs/asciidoc/production-ready-features.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -900,6 +900,9 @@ readinessProbe:
900900
periodSeconds: ...
901901
----
902902

903+
These health groups are only enabled automatically if the application is <<deployment.adoc#cloud-deployment-kubernetes,running in a Kubernetes environment>>.
904+
You can enable them in any environment using the configprop:management.health.probes.enabled[] configuration property.
905+
903906
NOTE: If an application takes longer to start than the configured liveness period, Kubernetes mention the `"startupProbe"` as a possible solution.
904907
The `"startupProbe"` is not necessarily needed here as the `"readinessProbe"` fails until all startup tasks are done, see <<production-ready-features.adoc#production-ready-kubernetes-probes-lifecycle,how Probes behave during the application lifecycle>>.
905908

0 commit comments

Comments
 (0)