Skip to content
This repository has been archived by the owner on Jul 18, 2019. It is now read-only.

First pass at adding resource requests to foreman. #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

clewis
Copy link

@clewis clewis commented Aug 13, 2018

These are very rough guesses based on what I see in SysDig relative to
the default request.cpu (2m).

These are very rough guesses based on what I see in SysDig relative to
the default request.cpu (2m).
@@ -27,6 +27,10 @@ spec:
- name: {{ .Chart.Name }}
image: "{{ .Values.utilitypod.image.repository }}:{{ .Values.utilitypod.image.tag }}"
imagePullPolicy: Always
resources:
request:
cpu: 10m
Copy link

@kr3cj kr3cj Aug 19, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You may have already seen this but I believe 10m means ten millicpu: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#meaning-of-cpu

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct. The default value is 2m, and sysdig says it's not even using that.

I don't like giving containers such tiny numbers. That's a great way to shoot yourself in the foot later, when a deployment needs to actually do something. I generally don't like going below 50m without a lot of history, but this one shows no CPU pulled for the whole 2 weeks visible in sysdig.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants