Merge branch '3.5.x' into 4.0.x

Closes gh-48946

Author: wilkinsona

documentation/spring-boot-docs/src/docs/antora/modules/how-to/pages/deployment/cloud.adoc

@@ -124,6 +124,8 @@ Because this shutdown processing happens in parallel (and due to the nature of d
 
 You can configure a sleep execution in a preStop handler to avoid requests being routed to a pod that has already begun shutting down.
 This sleep should be long enough for new requests to stop being routed to the pod and its duration will vary from deployment to deployment.
+The delay should be at least as long as the longest time it takes to process an in-flight request.
+You should not rely on the Spring Boot graceful shutdown period alone, as the platform will not be getting any liveness data in the period that the app is shutting down.
 
 If you're using Kubernetes 1.32 or up, the preStop handler can be configured by using the PodSpec in the pod's configuration file as follows:
 

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

@@ -1089,6 +1089,7 @@ When a Spring Boot application shuts down:
 |`REFUSING_TRAFFIC`
 |New requests are rejected
 |If enabled, xref:web/graceful-shutdown.adoc[graceful shutdown processes in-flight requests].
+HTTP probes also stop accepting traffic, so the availability states are not readily available externally.
 
 |Shutdown complete
 |N/A
@@ -1098,6 +1099,7 @@ When a Spring Boot application shuts down:
 |===
 
 TIP: See xref:how-to:deployment/cloud.adoc#howto.deployment.cloud.kubernetes.container-lifecycle[] for more information about Kubernetes deployment.
+In particular, it describes how to use the `preStop` hook to give your application time to shut down gracefully before Kubernetes kills it.