Service deployment in namespace with resource quota fails due to missing request and limit on queue-proxy

[raushan2016]

In what area(s)?

/area API
/area serving

What version of Knative?

0.5.x
0.6.x

Expected Behavior

User should be able to create knative service in namepsace's with resource quota

Actual Behavior

Knative service creation fails, as the queue-proxy doesn't have default resource request and limit set. Currently it only has request.cpu set to 25m. The current work around is create a LimitRange in the namespace. Similar issue was for istio 0.5 for the sidecar proxy , but with latest version it now has default resource request and limits for the side-car. It would be nice to have it for queue-proxy.

Steps to Reproduce the Problem

• Create a namespace
• Add resource quota to the namespace with request and limit
• Create a knative service.
• The deployment fails with missing request and limit
  message: 'pods "helloworld-go-k9lw9-deployment-6478957b64-hp4zh" is forbidden: failed quota: resource-quota: must specify limits.cpu,limits.memory,requests.cpu,requests.memory'

[raushan2016]

Will be part of 0.7