Update your ClowdApp templates to use template parameters for all CPU/memory requests and limits. The parameter names need to match the naming format (examples are in the implementation guide) 1. Open a temporary PR which deploys your app without resources stripped (a.k.a using ‘--no-remove-resources’) to invoke a smoke test that will “exercise” your app. Running the tests in this way should help better determine how much CPU/mem your apps realistically need during a PR check. (examples are in the implementation guide) 2. Use our ephemeral pod right-sizing grafana dashboard to determine the proper resource values for your containers. The implementation guide explains how to use this dashboard. The goal here is to observe the actual amount of CPU and memory that your app truly consumes and use the values here when setting the parameters in your deployment config. 3. Set the parameter values properly on your ephemeral deploy target in app-interface (examples are in the implementation guide) 4. Remove usage of bonfire’s --no-remove-resources option (if you were using it) 5. After making your template changes and adding the parameters to your ephemeral deployment configuration, make sure that your PR checks continue to work as they did before.