Uploaded image for project: 'Distributed Tracing'
  1. Distributed Tracing
  2. TRACING-3204

Remove resource limits for Tempo Operator but keep the resource.requests

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • rhosdt-2.9
    • None
    • Tempo
    • None
    • 1
    • Tracing Sprint # 237
    • Important

    Description

      Remove the resource limits from the Tempo Operator to avoid a situation similar to TRACING-3173

      Upstream issue: https://github.com/grafana/tempo-operator/issues/426

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. TRACING-3173 jaeger-operator pod restarting with OOMKilled with the default memory value

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          links to

          Web Link [KCS] Jaeger operator pod restarting in RHOCP 4

          GitHub openshift/openshift-docs#62410: Distributed tracing 2.9

          Web Link RHSA-2023:117866 Red Hat OpenShift distributed tracing 2.9.0 operator/operand containers

          Activity

            People

              rhn-support-iblancas Israel Blancas Alvarez
              rhn-support-ocasalsa Oscar Casal Sanchez
              Ishwar Kanse Ishwar Kanse
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: