Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-49791

Use /livez for Kubernetes scheduler liveness probe

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.18, 4.19
    • HyperShift
    • Low
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

          The kube scheduler pod should use the /livez endpoint rather than /healthz for its liveness probe.

      Version-Release number of selected component (if applicable):

      How reproducible:

          N/A

      Steps to Reproduce:

          N/A

      Actual results:

              livenessProbe:
          failureThreshold: 5
          httpGet:
            path: /healthz

      Expected results:

              livenessProbe:
          failureThreshold: 5
          httpGet:
            path: /livez

      Additional info:

              Unassigned Unassigned
              jonesbry Bryan Jones
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: