Commit e6ade05c authored by Hui Li's avatar Hui Li Committed by Phillip Webb

Clarify documentation for probe ports

Update the reference documentation to provide a better description of
the port that should be used for Kubernetes probes.

See gh-21650
parent 9dfb09c5
...@@ -894,18 +894,20 @@ You can then configure your Kubernetes infrastructure with the following endpoin ...@@ -894,18 +894,20 @@ You can then configure your Kubernetes infrastructure with the following endpoin
livenessProbe: livenessProbe:
httpGet: httpGet:
path: /actuator/health/liveness path: /actuator/health/liveness
port: liveness-port port: management-port
failureThreshold: ... failureThreshold: ...
periodSeconds: ... periodSeconds: ...
readinessProbe: readinessProbe:
httpGet: httpGet:
path: /actuator/health/readiness path: /actuator/health/readiness
port: liveness-port port: management-port
failureThreshold: ... failureThreshold: ...
periodSeconds: ... 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 <<deployment.adoc#cloud-deployment-kubernetes,running in a Kubernetes environment>>. These health groups are only enabled automatically if the application is <<deployment.adoc#cloud-deployment-kubernetes,running in a Kubernetes environment>>.
You can enable them in any environment using the configprop:management.health.probes.enabled[] configuration property. You can enable them in any environment using the configprop:management.health.probes.enabled[] configuration property.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment