You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: spring-boot-project/spring-boot-docs/src/docs/asciidoc/production-ready-features.adoc
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -894,18 +894,20 @@ You can then configure your Kubernetes infrastructure with the following endpoin
894
894
livenessProbe:
895
895
httpGet:
896
896
path: /actuator/health/liveness
897
-
port: liveness-port
897
+
port: management-port
898
898
failureThreshold: ...
899
899
periodSeconds: ...
900
900
901
901
readinessProbe:
902
902
httpGet:
903
903
path: /actuator/health/readiness
904
-
port: liveness-port
904
+
port: management-port
905
905
failureThreshold: ...
906
906
periodSeconds: ...
907
907
----
908
908
909
+
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.
910
+
909
911
These health groups are only enabled automatically if the application is <<deployment.adoc#cloud-deployment-kubernetes,running in a Kubernetes environment>>.
910
912
You can enable them in any environment using the configprop:management.health.probes.enabled[] configuration property.
0 commit comments