From f59d42c64fc7270f2bb0103baa5232e4b35ad5c3 Mon Sep 17 00:00:00 2001 From: Hui Li Date: Tue, 2 Jun 2020 16:15:10 +0900 Subject: [PATCH 1/2] Change liveness-port to management-port Change liveness-port to management-port in liveness and readiness probe example --- .../src/docs/asciidoc/production-ready-features.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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..e47d75c9f36f 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,14 +888,14 @@ 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: ... ---- From ca818548938391e026572338dfa9a11b9b76afb5 Mon Sep 17 00:00:00 2001 From: lihui Date: Wed, 3 Jun 2020 10:35:59 +0900 Subject: [PATCH 2/2] Add a note for management-port. --- .../src/docs/asciidoc/production-ready-features.adoc | 2 ++ 1 file changed, 2 insertions(+) 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 e47d75c9f36f..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 @@ -900,6 +900,8 @@ readinessProbe: 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.