Does anyone know how to override what seems to be the default LimitRange in GKE which sets the default request for CPU to 100m?
I've previously updated the limit to be 10m which is still overkill but better than the default using the following manifest;
apiVersion: v1
kind: LimitRange
metadata:
name: limits
namespace: default
spec:
limits:
- defaultRequest:
cpu: 10m
type: ContainerThis has since been overwritten back to 100m. Can I disable this behaviour?
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.
From reading the attached 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 here.