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

Misaligned OpenShift apiserver probe endpoints

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.18.0
    • 4.18.z
    • HyperShift
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • No
    • None
    • None
    • Done
    • Bug Fix
    • Update liveness and readiness probes associated with the OpenShift apiserver to use the /livez (for liveness probe) and /readyz (for readiness probe) endpoints instead of the /healthz endpoint.
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-54819. The following is the description of the original issue:

      Description of problem:

          The liveness and readiness probes associated with the OpenShift apiserver in HyperShift is misaligned with the probes used in OpenShift IPI.

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

          4.18

      How reproducible:

          Every time.

      Steps to Reproduce:

          1. Deploy a ROKS v4.18 (HyperShift) cluster.
          2. Check the openshift-apiserver deployment spec.
          

      Actual results:

          Liveness and readiness probes use the /healthz endpoint.

      Expected results:

          Liveness and readiness probes use the /livez and /readyz endpoints similar to OpenShift IPI.

      Additional info:

          - https://github.com/openshift/cluster-openshift-apiserver-operator/pull/612
          - https://github.com/openshift/cluster-openshift-apiserver-operator/pull/588

              Unassigned Unassigned
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Ke Wang Ke Wang
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: