<p>Does anyone know how to override what seems to be the default LimitRange in GKE which sets the default request for CPU to 100m? </p>

<p>I've previously updated the limit to be 10m which is still overkill but better than the default using the following manifest; </p>

<pre><code>apiVersion: v1
kind: LimitRange
metadata:
  name: limits
  namespace: default
spec:
  limits:
  - defaultRequest:
      cpu: 10m
    type: Container
</code></pre>

<p>This has since been overwritten back to 100m. Can I disable this behaviour? </p>

<p>Clearly I could update my manifest file to always include the request amount on containers but I'm interested to understand how this works in GKE and if it's documented.   </p>

Tim Reynolds
<p>From reading the <a href="https://github.com/pachyderm/pachyderm/issues/1892" rel="nofollow noreferrer">attached</a> github article, there is a Limit Range set within the default namespace. If you would like to change the Limit Range, you can create a Limit Range in a non-default namespace. You can read on how to create a Limit Range in a non default namespace <a href="https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/cpu-default-namespace/" rel="nofollow noreferrer">here</a>. </p>
