diff --git a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/production-ready-features.adoc b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/production-ready-features.adoc index 1fbbaba9b261..7dd53f0c0230 100644 --- a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/production-ready-features.adoc +++ b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/production-ready-features.adoc @@ -888,18 +888,20 @@ You can then configure your Kubernetes infrastructure with the following endpoin livenessProbe: httpGet: path: /actuator/health/liveness - port: liveness-port + port: management-port failureThreshold: ... periodSeconds: ... readinessProbe: httpGet: path: /actuator/health/readiness - port: liveness-port + port: management-port failureThreshold: ... periodSeconds: ... ---- +NOTE: `"management-port"` means the port that the actuator endpoints are available on. It could be the server port if a separate management port has not been configured or the `"management.server.port"` property if that has been explicitly configured. + These health groups are only enabled automatically if the application is <>. You can enable them in any environment using the configprop:management.health.probes.enabled[] configuration property.