Bug 1847086 - [IPI baremetal] baremetal-runtimecfg k8s health-check use hardcoded IPv4 local address (127.0.0.1)
Summary: [IPI baremetal] baremetal-runtimecfg k8s health-check use hardcoded IPv4 loca...
Keywords:
Status: CLOSED DUPLICATE of bug 1847082
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Yossi Boaron
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-15 15:51 UTC by Yossi Boaron
Modified: 2020-06-22 14:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-16 16:25:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.