[multi-container] How should Revision[CPU|Memory]Request defaults apply to revisions with multiple containers

[dprotaso]

Does applying this default still make sense?

I'd think RevisionCPURequest & RevisionMemoryRequest would imply totals for all user containers combined?

Now the Pod's requests/limits are a multiple of the number of containers

Originally posted by @dprotaso in #7167

[dprotaso]

/area API

[knative-housekeeping-robot]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh by adding the comment /remove-lifecycle stale.
Stale issues rot after an additional 30 days of inactivity and eventually close.
If this issue is safe to close now please do so by adding the comment /close.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/lifecycle stale

[dprotaso]

/remove-lifecycle stale

[mattmoor]

/lifecycle frozen

[evankanderson]

/kind spec

/assign @dprotaso

Is there work to be done here still? This bug just had a birthday.

/triage needs-user-input