Bug 1847086

Summary: [IPI baremetal] baremetal-runtimecfg k8s health-check use hardcoded IPv4 local address (127.0.0.1)
Product: OpenShift Container Platform Reporter: Yossi Boaron <yboaron>
Component: InstallerAssignee: Yossi Boaron <yboaron>
Installer sub component: OpenShift on Bare Metal IPI QA Contact: Amit Ugol <augol>
Status: CLOSED DUPLICATE Docs Contact:
Severity: unspecified    
Priority: unspecified CC: beth.white
Version: 4.5Keywords: Triaged
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-16 16:25:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yossi Boaron 2020-06-15 15:51:32 UTC 
Description of problem:

baremetal-runtimecfg (haproxy-monitor) sets/removes firewall rule that redirects API traffic to LB, it runs [1] to verify kube-api health status via the LB. 
 
It uses IPv4 localhost address (127.0.0.1)to communicate with the local LB, it should use 'localhost' to cover both IPv4 and IPv6 cases.

Additionally, based on [2] we should check 'readyz' endpoint and not 'healthz'  


[1] https://github.com/openshift/baremetal-runtimecfg/blob/master/pkg/utils/utils.go#L86
[2] https://github.com/openshift/installer/blob/master/docs/dev/kube-apiserver-health-check.md#load-balancer-health-check-probe
Comment 1 Beth White 2020-06-16 16:25:38 UTC 

*** This bug has been marked as a duplicate of bug 1847082 ***