When deploying a Spring Boot 4.x application to Tanzu Application Service (TAS) and accessing it through Tanzu Apps Manager, actuator-based information (health, metrics, etc.) as explained in https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/spring-boot-actuators.html fails to load.
Browser developer tools show a CORS error in the "/cloudfoundryapplication" request as shown in below screenshot:
Spring Boot 4
Starting with Spring Boot 4, Cloud Foundry–specific functionality has been modularized and is no longer automatically enabled by the presence of Actuator alone.
The Cloud Foundry actuator integration, including the /cloudfoundryapplication endpoint and its associated CORS handling, is now provided by a separate Spring Boot module.
If the application does not include the Cloud Foundry starter:
the /cloudfoundryapplication endpoint may still be partially mapped, but Cloud Foundry–specific behavior (including CORS configuration) is not fully applied. As a result, browser-based requests from Tanzu Apps Manager fail due to missing CORS headers.
Add the Cloud Foundry starter dependency to the Spring Boot 4 application.
After rebuilding and redeploying the application, the /cloudfoundryapplication endpoint will correctly include the required CORS headers and Tanzu Apps Manager will be able to access actuator data successfully.
The documentation will reflect this change when Spring Boot 4.0.2 is released on January 22, 2026.
If after adding the Cloud Foundry starter dependency you see a ClassNotFoundException: RestTemplateBuilder Exception, and you are using Spring Boot 4.0.0 or 4.0.1, refer to this KB to solve the issue.