Skip to content

Commit 7edde21

Browse files
committed
Merge branch '4.0.x'
Closes spring-projectsgh-50016
2 parents 767444c + dd6bc60 commit 7edde21

File tree

1 file changed

+3
-3
lines changed
  • documentation/spring-boot-docs/src/docs/antora/modules/reference/pages/actuator

1 file changed

+3
-3
lines changed

documentation/spring-boot-docs/src/docs/antora/modules/reference/pages/actuator/endpoints.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -976,10 +976,10 @@ It could be the main web server port or a separate management port if the `"mana
976976
These health groups are automatically enabled.
977977
You can disable them by using the configprop:management.endpoint.health.probes.enabled[] configuration property.
978978

979-
NOTE: If an application takes longer to start than the configured liveness period, Kubernetes mentions the `"startupProbe"` as a possible solution.
980-
Generally speaking, the `"startupProbe"` is not necessarily needed here, as the `"readinessProbe"` fails until all startup tasks are done.
979+
NOTE: If an application takes longer to start than the configured liveness period, Kubernetes https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#when-should-you-use-a-startup-probe[mentions the `"startupProbe"` as a possible solution].
980+
Generally speaking, the `"startupProbe"` is not necessarily needed here as the `"readinessProbe"` fails until all startup tasks are done.
981981
This means your application will not receive traffic until it is ready.
982-
However, if your application takes a long time to start, consider using a `"startupProbe"` to make sure that Kubernetes won't kill your application while it is in the process of starting.
982+
However, if your application takes a long time to start, consider https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-startup-probes[configuring a `"startupProbe"`] that uses the liveness HTTP probe to make sure that Kubernetes won't kill your application while it is in the process of starting.
983983
See the section that describes xref:actuator/endpoints.adoc#actuator.endpoints.kubernetes-probes.lifecycle[how probes behave during the application lifecycle].
984984

985985
If your Actuator endpoints are deployed on a separate management context, the endpoints do not use the same web infrastructure (port, connection pools, framework components) as the main application.

0 commit comments

Comments
 (0)