OKD 3.11 Ansible Inventory [lb] 中的多个主机
Multiple hosts in [lb] of OKD 3.11 Ansible Inventory
我打算安装 "MULTIPLE MASTERS USING NATIVE HA WITH CO-LOCATED CLUSTERED ETCD" 并且没有外部负载平衡，所以我知道我必须通过在清单文件中提供以下部分来启用本机 HA
# Specify load balancer host
[lb]
lb.example.com
我们可以在这里提供多个大师作品吗？如果不是那么如果上述节点出现故障会发生什么？
超过一 [lb] 的主机没有用。对于每个 [lb] 主机，将执行 openshift_loadbalancer 角色，没有任何 IP 共享等
根据Load Balancing For HA Master Infrastructure：
Out of the box, the OpenShift has the ability to install an HAProxy instance on a host you designate as a lightweight load balancer between masters in Native HA mode. However, this only creates another single point of failure. It is much preferred to integrate an enterprise load balancer (LB) such as an F5 Big-IP™ or a Citrix Netscaler™ appliance. This integration does add some complexity to the install process. We attempt to explain those options below.
所以如果你想要HA API负载均衡你必须根据Load Balancing For HA Master Infrastructure
自行配置高级均衡方案作为外部LB
If the API Server load balancer is not available, nodes cannot report their status, all their pods are marked dead, and the pods' endpoints are removed from the service
我打算安装 "MULTIPLE MASTERS USING NATIVE HA WITH CO-LOCATED CLUSTERED ETCD" 并且没有外部负载平衡，所以我知道我必须通过在清单文件中提供以下部分来启用本机 HA
# Specify load balancer host
[lb]
lb.example.com
我们可以在这里提供多个大师作品吗？如果不是那么如果上述节点出现故障会发生什么？
超过一 [lb] 的主机没有用。对于每个 [lb] 主机，将执行 openshift_loadbalancer 角色，没有任何 IP 共享等
根据Load Balancing For HA Master Infrastructure：
Out of the box, the OpenShift has the ability to install an HAProxy instance on a host you designate as a lightweight load balancer between masters in Native HA mode. However, this only creates another single point of failure. It is much preferred to integrate an enterprise load balancer (LB) such as an F5 Big-IP™ or a Citrix Netscaler™ appliance. This integration does add some complexity to the install process. We attempt to explain those options below.
所以如果你想要HA API负载均衡你必须根据Load Balancing For HA Master Infrastructure
自行配置高级均衡方案作为外部LBIf the API Server load balancer is not available, nodes cannot report their status, all their pods are marked dead, and the pods' endpoints are removed from the service