Bug 1836038

Summary: Azure IPI: Both Internal and External load balancers for kube-apiserver should use /readyz
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: InstallerAssignee: Abu Kashem <akashem>
Installer sub component: openshift-installer QA Contact: Etienne Simard <esimard>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: bleanhar, esimard, ffranz, jminter, mgahagan, mjudeiki, wking, xxia
Version: 4.5Keywords: Upgrades
Target Milestone: ---   
Target Release: 4.4.z   
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-02 11:18:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1828382    
Bug Blocks: 1840230    

Comment 3 Etienne Simard 2020-05-26 15:07:37 UTC
Verified with: 4.4.0-0.nightly-2020-05-22-051026

I confirmed the following probes are in use on my working Azure cluster:

public-lb:

~~~
    "name": "api-internal-probe",
    "numberOfProbes": 3,
    "port": 6443,
    "protocol": "Https",
    "provisioningState": "Succeeded",
    "requestPath": "/readyz",
    "resourceGroup": "qe-cluster-kdrvz-rg",
    "type": "Microsoft.Network/loadBalancers/probes"
~~~

internal-lb:

~~~

    "name": "sint-probe",
    "numberOfProbes": 3,
    "port": 22623,
    "protocol": "Https",
    "provisioningState": "Succeeded",
    "requestPath": "/healthz",
    "resourceGroup": ""qe-cluster-kdrvz-rg",
    "type": "Microsoft.Network/loadBalancers/probes",

    "name": "api-internal-probe",
    "numberOfProbes": 3,
    "port": 6443,
    "protocol": "Https",
    "provisioningState": "Succeeded",
    "requestPath": "/readyz",
    "resourceGroup": "qe-cluster-kdrvz-rg",
    "type": "Microsoft.Network/loadBalancers/probes"
~~~

Comment 5 errata-xmlrpc 2020-06-02 11:18:33 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2310