Support having pod resource request != pod resource limit

[JamesMurkin]

Problem Currently the executor reports pod usage to the server as simply the pod request values.

This restricts use to:

• Pod request = Pod limit

If request != limit, it could be the case that the executor over allocates the cluster (potentially by a lot if request and limit significantly differ).

Potential solution The executor should report pod usage as: max (pod request, pod actual usage)

This means when the pod usage > pod request, we don't over allocate the cluster.

This will be further complicated if we want to start doing preemption based on pods being over the request

Considerations

• How accurate we can get pod current actual usage
• How much impact we have on the Kubernetes API, if we ask for the real usages too frequently when there are many pods

[dave-gantenbein]

Please add your planning poker estimate with ZenHub @richscott

[richscott]

It's not letting me vote - I have all ad-blockers off, etc. When I attempt to click on an estimate value, I am seeing inside the Firefox web console:

[GraphQL error]: Message: "Forbidden", Location: [
  {
    "line": 2,
    "column": 3
  }
], Path: [
  "setEstimationVote"

[richscott]

Just tried it with Safari, and I get the "Forbidden" GraphQL network response as well. Does Zenhub require that a ticket be "opened" for point voting, or some such?