Uploaded image for project: 'OpenShift Installer'
  1. OpenShift Installer
  2. CORS-3289

[capi[aws][bug] Fix API's LB Target Health Check attributes when using HTTP or HTTPS

XMLWordPrintable

    • 5
    • OpenShift SPLAT - Sprint 252

      Issue:

      • Kubernetes API on OpenShift requires advanced health check configuration ensure graceful termiantion[1] works correctly. The health check protocol must be HTTPS testing the path /readyz.
        • Currently CAPA support standard configuration (health check probe timers) and for path, when using HTTP or HTTPS is selected.
      • MCS listener/target must use HTTPS health check with custom probe periods too.

      Steps to reproduce:

      • Create CAPA cluster
      • Check the Target Groups created to route traffic to API (6443), for both Load Balancers (int and ext)

      Actual results:

      • TCP health check w/ default probe config

      Expected results:

      • HTTPS health check evaluating /readyz path
      • Check parameters: 2 checks in the interval of 10s, using 10s of timeout

       

      References:

            rhn-support-mrbraga Marco Braga
            rhn-support-mrbraga Marco Braga
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: