Комментарии:
This is just what I was studying last night! Awesome!
ОтветитьKeep up the good work 👍
Ответитьgreat video. not sure though why the human appearance is necessary
Ответитьis request and limit confined to containers or pods? because if i specify request and limit values to pod where pod have multiple containers then in that case will all the containers get adequate amount of resource?
Ответитьtoo bad you can't throttle memory with swap 🤔
ОтветитьNice video but one thing is not so clear: How to check the resources the pods are actually using?
Lets say I have a cluster running and have assigned some resources and limits. How can I check if those values are good for my application?
kubectl top and describe give very little information that is hard to relate. Is there a good resource about this?
Thanks! In my case I had to use Mi as unity instead of Mib.
ОтветитьThanks!!
ОтветитьYou say the values for each container are additive. Does this mean that if I have three pods, best practice should mean that the limt of 1 needs to be split between the three pods. i.e. I currently have limit 0.5 for main pod and 0.25 for the other two. Then the same for the requests. I have 0.6 for the the main pod and 0.2 for the other two.
ОтветитьSandeep, I believe having development and production seperated by namespaces is not a good practice. The development load will affect production load. What do you think about it?
ОтветитьHello! This's a very clear video about resources. Thank you very much. Keep going.
Ответитьwhat about GPU though?
ОтветитьWhat about swap RAM ?
ОтветитьMy application needs SwAp Memory
ОтветитьWell presented, and exactly what I was looking for Thank you!
ОтветитьCan you tell us what is hard limit in quota
Ответитьthank you for such a great video. you're amazing <3
Ответитьthrottling and the area between over-requested but below a hard limit is still unclear on what kubernetes really does
Ответитьso touching for an excellent video
Ответитьthanks, short and clear
ОтветитьVery well presented information! Why couldn't the Kubernetes documentation just say "milli-cores" explicitly, I had to dig around to find that.
Ответитьif I'm using GKE, where do I go to evaluate how much a resource should request or be limited by?
ОтветитьGreat presentation!
ОтветитьVery well explained!
ОтветитьThanks Sandeep, perfect presentation!
ОтветитьIs there any way to restrict some core shall not be used by Kubernetes on host machines. For example Server-1 having core 0-31 where I wanted to keep 1,2,3,4 CPU as isolated and core 1,2,3,4 shall not be used by K8s. any configuration for this goal ?
ОтветитьWhat about GPU resources? These are often more scarce than CPU memory of CPU cylces.
ОтветитьHere, is memory component similar to RAM only right?
Ответитьsimple and to the point :)
Ответить