Please fill in the following information:

 
Issue description

Step 2.2 of the GE provides a WildFlyServer resource with requests and limits set very low. While requests are necessarily set to 10% of a core (100m) to ensure correct autoscaling behaviour, limits do not need to be as low as they are.

Consequently they cause the application server to start up too slowly, and the application to be terminated before it manages to report readiness.

Steps to reproduce:

RHLS production lab environment in eu-central-1, following the exercise steps, the server never completes the startup. Consult the attached screenshot.

Workaround:

Set the CPU limits to a higher value, such as 500m.