Skip to content

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

New issue
New issue
Open
Open
[multi-container] How should Revision[CPU|Memory]Request defaults apply to revisions with multiple containers#7240
Assignees
dprotaso
Labels
area/APIAPI objects and controllershelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/specDiscussion of how a feature should be exposed to customers.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.triage/acceptedIssues which should be fixed (post-triage)
Milestone
Icebox
@dprotaso

Description

@dprotaso
dprotaso
opened on Mar 13, 2020

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

Metadata

Metadata

Assignees

Labels

area/APIAPI objects and controllershelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/specDiscussion of how a feature should be exposed to customers.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.triage/acceptedIssues which should be fixed (post-triage)

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions