Kops: Document default cpu limits and how to change them

[ferrouswheel]

I was confused as to why and where cpu requests of 100m per container were being set. It would be great for this to be documented or part of the kops cluster spec.

Limits were added and merged as part of #974

This issue is continued from the closed issue #471 where another user asked "Is there any way to prevent kops from creating this LimitRange?"

[chrislovecnm]

This is actually documented on the kubernetes.io site. There is not way at this point to override the limits, you have to adjust ten after install. To be clear this is the default limits.

[ferrouswheel]

Thanks Chris, do you mind pointing out where the defaults are documented on the kubernetes.io site? I've tried googling and looking in relevant sections, and while I can find everything about how to control limit ranges I can't find anything about the default CPU request limit for containers.

[chrislovecnm]

https://kubernetes.io/docs/tasks/administer-cluster/cpu-memory-limit/#apply-a-limit-to-the-namespace

[ferrouswheel]

Those documents tell you how to set a default for a namespace. My issue is the lack of documentation around what the default is for Kops out-of-the-box.

While Kubernetes may have this as a default setting somewhere - Kops explicitly had a limit included in the referenced pull request here: https://github.com/kubernetes/kops/pull/974/files#diff-704448baec97bf365430f4c1b12d24e9

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[nhooyr]

Could this please be reopened?