Set proper boot actuator endpoint configuration when deploying apps.

[CEDDM]

Description:
The info endpoint is no more enabled by default with Spring Boot 2.5 https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.5-Release-Notes#secure-info-endpoint
This causes the app to be stucked in "Deploying" state in Kubernetes with this error : Readiness probe failed: HTTP Probe failed with statuscode: 404

Release versions:
Tested with SCDF 2.9.1 and Spring Boot 2.5.5 under microk8s 1.18.20

Steps to reproduce:
Create a dummy processor and deploy it in Kubernetes with a simple stream like time | my-processor | log

Additional context:
A simple workaround is to add management.endpoints.web.exposure.include=health,info in application.properties to enable info endpoint.
But wouldn't it be nice if Skipper does that for us ?

[jvalkeal]

We've been trying not to tweak setting too much as we don't know what user is running. On our normal apps we chose to re-enable those endpoints in apps itself.

There is a config setting Common Application Properties where you could do this, would it work for you?

[CEDDM]

Yes sure ! That would work.
But I'm afraid it might be complicated for SCDF beginners to understand why their app is not in 'Deployed' status.
I lost a couple of hours to understand why my apps didn't work anymore after upgrading Spring Boot

[markpollack]

I agree, we already set many boot properties so that the user doesn't have to, this one sounds quite important. I am a bit surprised to hear about this since, afaik, we don't do anything special regarding command app properties when deploying streams in our acceptance tests. I'll ping the group from input. Thanks for reporting.

[corneil]

My suggestion would be to make sure the samples have these properties added and that we document the need for adding management.endpoints.web.exposure.include=health,info,bindings