Goal:

• As OCP developer I would like to deploy OpenShift using the installer/CAPA to provision the infrastructure setting the health check parameters to satisfy the existing terraform implementation
•  

Issue:

• The API listeners is created exposing different health check attributes than the terraform implementation. There is a bug to fix to the correct path when using health check protocol HTTP or HTTPS (CORS-3289)
• The MCS listener, created using the AdditionalListeners option from the *LoadBalancer, requires advanced health check configuration to satisfy terraform implementation. Currently CAPA sets the health check with standard TCP or default path ("/") when using HTTP or HTTPS protocol.

Steps to reproduce:

• Create CAPA cluster
• Check the Target Groups created to route traffic to MCS (22623), for internal Load Balancers

Actual results:

• TCP or HTTP/S health check w/ default probe config

Expected results:

• API listeners with target health check using HTTPS evaluating /healthz path
• MCS listener with target health check using HTTPS evaluating /healthz path
• Check parameters: 2 checks in the interval of 10s, using 10s of timeout

References:

•  [1] API graceful termination: https://github.com/openshift/installer/blob/master/docs/dev/kube-apiserver-health-check.md 
• documentation: https://docs.openshift.com/container-platform/4.15/installing/installing_platform_agnostic/installing-platform-agnostic.html#installation-load-balancing-user-infra_installing-platform-agnostic 
• Current terraform setup: https://github.com/openshift/installer/blob/master/data/data/aws/cluster/vpc/master-elb.tf#L86-L94