title: "Limits" property ignored when deploying a container in a Kubernetes cluster
body: <p>I am deploying a container in Google Kubernetes Engine with this YAML fragment:</p>
  
  <pre><code>    spec:
        containers:
        - name: service
          image: registry/service-go:latest
          resources:
            requests:
             memory: "20Mi"
             cpu: "20m"
            limits:
             memory: "100Mi"
             cpu: "50m"
  </code></pre>
  
  <p>But it keeps taking 120m. <strong>Why is "limits" property being ignored?</strong> Everything else is working correctly. If I request 200m, 200m are being reserved, but limit keeps being ignored.</p>
  
  <p><a href="https://i.stack.imgur.com/9zN6j.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/9zN6j.png" alt="enter image description here"></a></p>
  
  <p>My Kubernetes version is 1.10.7-gke.1</p>
  
  <p>I only have the default namespace and when executing</p>
  
  <blockquote>
    <p>kubectl describe namespace default</p>
  </blockquote>
  
  <pre><code>Name:         default
  Labels:       &lt;none&gt;
  Annotations:  &lt;none&gt;
  Status:       Active
  
  No resource quota.
  
  Resource Limits
   Type       Resource  Min  Max  Default Request  Default Limit  Max Limit/Request Ratio
   ----       --------  ---  ---  ---------------  -------------  -----------------------
   Container  cpu       -    -    100m             -              -
  </code></pre>