Uploaded image for project: 'OpenShift Workloads'
  1. OpenShift Workloads
  2. WRKLDS-358

Expose additional information about GC and Quota under /debug endpoint

    XMLWordPrintable

Details

    • Story
    • Resolution: Unresolved
    • Critical
    • None
    • None
    • Workloads Sprint 208, Workloads Sprint 210, Workloads Sprint 211, Workloads Sprint 212, Workloads Sprint 214, Workloads Sprint 215, Workloads Sprint 216, Workloads Sprint 217, Workloads - 4.12, Workloads Sprint 225, Workloads Sprint 226, Workloads Sprint 227, Workloads Sprint 228, Workloads Sprint 229, Workloads Sprint 230, Workloads Sprint 231, Workloads Sprint 232, Workloads Sprint 233

    Description

      Currently if GC or quota experience problems when reading discovery we don't expose that information anywhere else than just in kube-controller-manager logs. We would like to go degraded with kcm-o when we know that either GC or quota is having issues. This should help identifying issues like "my namespace is stuck in terminating".

      For this reason we want to expose the information about discover problems under /debug endpoint of kcm.

      Resources:
      Exposing GC graph info under /debug: https://github.com/kubernetes/kubernetes/pull/66623
      Arch call notes: https://docs.google.com/document/d/1x50GTpboRSGOIKHjyWyaN8Q4p4jgTP2Bndw8kdqyIfU/edit#heading=h.2lffczpupyq6

      Attachments

        Issue Links

          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. WRKLDS-637 ClusterResourceQuota controller: Expose metrics about resource discovery

          • 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.
          • To Do
          relates to

          Bug - A problem which impairs or prevents the functions of the product. OCPBUGS-5806 kube-controller-manager crashes when kubernetes API is down

          • 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.
          • New

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: WRKLDS

              People

                fkrepins@redhat.com Filip Krepinsky
                maszulik1@redhat.com Maciej Szulik
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated: