-
Bug
-
Resolution: Obsolete
-
Normal
-
None
-
4.13, 4.12, 4.11
-
Moderate
-
No
-
6
-
OSDOCS Sprint 243, OSDOCS Sprint 244, OSDOCS Sprint 245, OSDOCS Sprint 246, OSDOCS Sprint 247, OSDOCS Sprint 248, OSDOCS Sprint 249, OSDOCS Sprint 250, OSDOCS Sprint 251
-
9
-
False
-
-
N/A
-
Release Note Not Required
Description of problem:
The `Load balancing requirements for user-provisioned infrastructure` section is under vsphere installation which confuses the customer if the configuration and healthcheck endpoints (mentioned under NOTE) are applicable only to Vsphere UPI clusters or to other platforms UPI clusters as well.
Version-Release number of selected component (if applicable):
4.11,4.12,4.13
How reproducible:
100%
The main agenda of this DOCBUG is to replace the Load balancing requirement section to a different location to make it Generic and applicable to every UPI/IPI cluster where customer need help in On-premise external load balancer setup. Another agenda of this DOCBUFG is to update the `Sample API and application Ingress load balancer configuration` with valid HTTP checks. Currently it only has TCP healthchecks example.
Additional info:
If a customer have cluster on BareMetal, RHEV, OpenStack etc. they question us back that the healthcheck endpoint mentioned under NOTE are only applicable to Vsphere and not to other platforms. DOC LOCATION: Load balancing requirements for user-provisioned infrastructure: https://docs.openshift.com/container-platform/4.13/installing/installing_vsphere/installing-vsphere.html#installation-load-balancing-user-infra_installing-vsphere Example load balancer configuration for user-provisioned clusters: https://docs.openshift.com/container-platform/4.13/installing/installing_vsphere/installing-vsphere.html#installation-load-balancing-user-infra-example_installing-vsphere