Uploaded image for project: 'Product Technical Learning'
  1. Product Technical Learning
  2. PTL-14001

DO480:ch09s05 : feedback about using cpu limits

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • DO480 - ACM2.4-en-5-20221130
    • DO480
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • 9
    • ROLE
    • en-US (English)

      Please fill in the following information:


      URL: https://role.rhu.redhat.com/rol-rhu/app/courses/do480-2.4/pages/ch09s05 
      Reporter RHNID: chetan-rhls
      Section Title:        Multicluster Configuration Management with RHACS                                                                 

      Issue description: feedback from kniederw@redhat.com   :

       In do480-2.4/pages/ch09s05 we have the following sentence: "For example, defining requests and limits for CPU and memory is a best practice, but nothing prevents you from creating a deployment without such limits."

      While CPU requests, memory limits and requests are surely a good idea, we should not propose CPU limits as best practice. CPU limits are a controversial topic and cause a lot of confusion for customers.

      I (as a TAM) would advise to rephrase this part and exclude CPU limits. AFAIK the official Red Hat strategy is not to propose CPU limits as best practices, but leave this as a choice for customers. We usually elaborate on the pros/cons of having CPU limits, but do not advise it as best practice. Explanation about the controversy can be found here:  https://home.robusta.dev/blog/stop-using-cpu-limits

       

      Steps to reproduce:

       

      Workaround:

       

      Expected result:

            gls-curriculum-ocp-core@redhat.com PTL - OCP Platform Team
            chetan-rhls Chetan Tiwary
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: