Setting Resource Requests and Limits in Kubernetes


    In this episode of Kubernetes Best Practices, Sandeep Dinesh shows how Kubernetes resource requests and limits can help you keep your containers under control.

    See the associated article here →

    Requests and Limits Documentation →
    Resource Quota Documentation →
    Limit Range CPU Documentation →
    Limit Range Memory Documentation →
    Kubernetes Engine Cluster Autoscaler →
    Pod Priority →
    Google Kubernetes Engine →

    Take a look at more Kubernetes Best Practices videos here →
    Subscribe to the Cloud channel →


    Previous articleDevOps Best Practices | DevOps Tutorial For Beginners | What Is DevOps Tutorial | Simplilearn
    Next articleTutoriel Docker pour débutants [COURS COMPLET en 1 heures]


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

    2. 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?

    3. I still can't understand what is defaultRequest. About what kind of request are we talking about? We can limit resources per let's say http request for container? And that's the default value specified, if I don't specify for a container? (Sorry this is first video I see from this channel)