GKE LimitRange limits defaults cpu to 100m












1














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: Container


This 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.










share|improve this question






















  • This might help. stackoverflow.com/questions/33391748/…
    – Ananthu R V
    Nov 12 at 10:39










  • Possible duplicate of How to reduce CPU limits of kubernetes system resources?
    – Ananthu R V
    Nov 12 at 10:39










  • @AnanthuRV So I've tried setting the limit to a lower value however it was overwritten as stated in my question.
    – Tim Reynolds
    Nov 12 at 14:04












  • Can you try giving 10 instead of 10m. Kubernetes example seems to be like that raw.githubusercontent.com/kubernetes/website/master/content/en/…
    – Ananthu R V
    Nov 13 at 7:32






  • 1




    I saw similar behaviour where my default limits that I've changed had been overridden :/
    – Bartosz Hernas
    Dec 20 at 10:07
















1














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: Container


This 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.










share|improve this question






















  • This might help. stackoverflow.com/questions/33391748/…
    – Ananthu R V
    Nov 12 at 10:39










  • Possible duplicate of How to reduce CPU limits of kubernetes system resources?
    – Ananthu R V
    Nov 12 at 10:39










  • @AnanthuRV So I've tried setting the limit to a lower value however it was overwritten as stated in my question.
    – Tim Reynolds
    Nov 12 at 14:04












  • Can you try giving 10 instead of 10m. Kubernetes example seems to be like that raw.githubusercontent.com/kubernetes/website/master/content/en/…
    – Ananthu R V
    Nov 13 at 7:32






  • 1




    I saw similar behaviour where my default limits that I've changed had been overridden :/
    – Bartosz Hernas
    Dec 20 at 10:07














1












1








1







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: Container


This 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.










share|improve this question













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: Container


This 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.







kubernetes google-cloud-platform google-kubernetes-engine gke






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 10 at 12:50









Tim Reynolds

316113




316113












  • This might help. stackoverflow.com/questions/33391748/…
    – Ananthu R V
    Nov 12 at 10:39










  • Possible duplicate of How to reduce CPU limits of kubernetes system resources?
    – Ananthu R V
    Nov 12 at 10:39










  • @AnanthuRV So I've tried setting the limit to a lower value however it was overwritten as stated in my question.
    – Tim Reynolds
    Nov 12 at 14:04












  • Can you try giving 10 instead of 10m. Kubernetes example seems to be like that raw.githubusercontent.com/kubernetes/website/master/content/en/…
    – Ananthu R V
    Nov 13 at 7:32






  • 1




    I saw similar behaviour where my default limits that I've changed had been overridden :/
    – Bartosz Hernas
    Dec 20 at 10:07


















  • This might help. stackoverflow.com/questions/33391748/…
    – Ananthu R V
    Nov 12 at 10:39










  • Possible duplicate of How to reduce CPU limits of kubernetes system resources?
    – Ananthu R V
    Nov 12 at 10:39










  • @AnanthuRV So I've tried setting the limit to a lower value however it was overwritten as stated in my question.
    – Tim Reynolds
    Nov 12 at 14:04












  • Can you try giving 10 instead of 10m. Kubernetes example seems to be like that raw.githubusercontent.com/kubernetes/website/master/content/en/…
    – Ananthu R V
    Nov 13 at 7:32






  • 1




    I saw similar behaviour where my default limits that I've changed had been overridden :/
    – Bartosz Hernas
    Dec 20 at 10:07
















This might help. stackoverflow.com/questions/33391748/…
– Ananthu R V
Nov 12 at 10:39




This might help. stackoverflow.com/questions/33391748/…
– Ananthu R V
Nov 12 at 10:39












Possible duplicate of How to reduce CPU limits of kubernetes system resources?
– Ananthu R V
Nov 12 at 10:39




Possible duplicate of How to reduce CPU limits of kubernetes system resources?
– Ananthu R V
Nov 12 at 10:39












@AnanthuRV So I've tried setting the limit to a lower value however it was overwritten as stated in my question.
– Tim Reynolds
Nov 12 at 14:04






@AnanthuRV So I've tried setting the limit to a lower value however it was overwritten as stated in my question.
– Tim Reynolds
Nov 12 at 14:04














Can you try giving 10 instead of 10m. Kubernetes example seems to be like that raw.githubusercontent.com/kubernetes/website/master/content/en/…
– Ananthu R V
Nov 13 at 7:32




Can you try giving 10 instead of 10m. Kubernetes example seems to be like that raw.githubusercontent.com/kubernetes/website/master/content/en/…
– Ananthu R V
Nov 13 at 7:32




1




1




I saw similar behaviour where my default limits that I've changed had been overridden :/
– Bartosz Hernas
Dec 20 at 10:07




I saw similar behaviour where my default limits that I've changed had been overridden :/
– Bartosz Hernas
Dec 20 at 10:07












1 Answer
1






active

oldest

votes


















0














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.






share|improve this answer





















  • Yea, I think the only way around this is to not use the default namespace. We've just set the limit on all containers now
    – Tim Reynolds
    Dec 20 at 14:23











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53239126%2fgke-limitrange-limits-defaults-cpu-to-100m%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














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.






share|improve this answer





















  • Yea, I think the only way around this is to not use the default namespace. We've just set the limit on all containers now
    – Tim Reynolds
    Dec 20 at 14:23
















0














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.






share|improve this answer





















  • Yea, I think the only way around this is to not use the default namespace. We've just set the limit on all containers now
    – Tim Reynolds
    Dec 20 at 14:23














0












0








0






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.






share|improve this answer












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.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 16 at 18:28









Jason

3988




3988












  • Yea, I think the only way around this is to not use the default namespace. We've just set the limit on all containers now
    – Tim Reynolds
    Dec 20 at 14:23


















  • Yea, I think the only way around this is to not use the default namespace. We've just set the limit on all containers now
    – Tim Reynolds
    Dec 20 at 14:23
















Yea, I think the only way around this is to not use the default namespace. We've just set the limit on all containers now
– Tim Reynolds
Dec 20 at 14:23




Yea, I think the only way around this is to not use the default namespace. We've just set the limit on all containers now
– Tim Reynolds
Dec 20 at 14:23


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53239126%2fgke-limitrange-limits-defaults-cpu-to-100m%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Schultheiß

Liste der Kulturdenkmale in Wilsdruff

Android Play Services Check