Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-6399

Does the /healthz endpoint checks all it need to check?

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Envoy
    • None
    • False
    • None
    • False

      Recently one of my customer hit the bug which we know that it has been fixed in ossm 2.4, however we are wondering if we can improve on the /healthz endpoint, as at that time, all the `istio-cni-node` pods are ready and health, but in reality, no new pods can be created because of the token expired, in that case, if the `istio-cni-node` failed the liveness probe and triggered an auto restart, the issue could be resolved temporarily, hence we are creating this ticket to see if we can improve on it
      I am not sure besides token issue, what other potential issue may cause the similar impact that block new pod creation?

            Unassigned Unassigned
            rhn-support-nsu CHU LIN Su
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: