Enhancement: Warn on resources out of proportion for simple builds

[mcandre]

Really simple builds, such as yum/apt/apk, wget/curl, tar/gunzip; or ADD/COPY of a static artifact, do not require much in the way of resources to quickly and successfully complete a build. I wonder if OpenShift could detect these opportunities for driving down cost, by reminding the user to set more appropriate resource constraints.

Even with the implicit git clone that often runs as part of the build process, 100m cpu request, 100Mi memory request, with 1 cpu and 1Gi memory limits, is more than sufficient for OpenShift to gallop through these basic builds. More intensive builds involving compilation or database daemons often don't need more than 1 cpu, 1Gi memory (C, C++, Go); or 1 cpu, 4Gi (Haskell, PostgreSQL) to work well.

And so financiers would appreciate if OpenShift could detect such simple builds, such as by checking Dockerfiles for more complicated build commands, and recommending to administrators that resources be lowered. I think this is technically possible. Do you think this would this deliver a lot of value to customers with a reasonably maintainable whitelist of lean Dockerfile build commands?

Where requests are far above these values (or worse, match the limits), then OpenShift could assist users in keeping costs down by recommending that resources be lowered.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.