Hi all
We have a situation where our pods need a load of cpu on startup only and it
seems that the limits for CPU that we have specified in our deployment is
throttling the pod on startup and causing it to take over 2 mins to start. If
we removed the limits configured in our deployment then start up is in seconds.
e.g this
resources:
limits:
cpu: 600m
memory: 768Mi
requests:
cpu: 600m
memory: 768Mi
is replace by this
resources:
limits:
cpu: 600m
memory: 768Mi
requests:
memory: 768Mi
Means startup in under 6 seconds.
Ideally we would like to be able to apply some sort of cpu limits after the pod
has started. Does anyone know if this can be achieved?
Thanks in advance
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.
