A service review asks for lower maximum concurrency and a bounded number of instances. Those settings affect different resource boundaries. Reducing concurrency does not set a project spending cap, and reducing the maximum instance count does not prove the service will meet its latency objective. A useful review states the supplied constraint and the evidence needed after applying it.
Use the Cloud Run adapter to change one setting at a time. Its state makes the before and after values visible without starting the container. Then inspect how image identity, ingress and caller access belong in the same release discussion. The training values are scenario requirements, not performance recommendations. In production, measure the relevant request mix and dependency behavior before attributing an improvement to a configuration change.
Change the requested setting, preserve the artifact, and measure behavior separately.