This may not be critical. As far as I see, even without the health monitor, API requests are retried(?).
Anyway, by adding the health monitor, haproxy config inside the Amphpora instance will be updated as follows:
[without health monitor]
backend 7d5d4323-f382-4a85-a965-4fcedd8c77f2:199362ee-e305-4ebf-947a-d3c155341ac9 mode tcp balance roundrobin fullconn 50000 option allbackups timeout connect 5000 timeout server 50000 server 91d6a444-6986-49c7-b46a-a17838d7a638 10.5.5.23:6443 weight 1 server 0e91354d-1f60-40d2-b748-d4e6be491ebe 10.5.5.66:6443 weight 1
[with TLS-HELLO health monitor]
backend 7d5d4323-f382-4a85-a965-4fcedd8c77f2:199362ee-e305-4ebf-947a-d3c155341ac9 mode tcp balance roundrobin timeout check 10s option ssl-hello-chk fullconn 50000 option allbackups timeout connect 5000 timeout server 50000 server 91d6a444-6986-49c7-b46a-a17838d7a638 10.5.5.23:6443 weight 1 check inter 5s fall 3 rise 4 server 0e91354d-1f60-40d2-b748-d4e6be491ebe 10.5.5.66:6443 weight 1 check inter 5s fall 3 rise 4
This may not be critical. As far as I see, even without the health monitor, API requests are retried(?).
Anyway, by adding the health monitor, haproxy config inside the Amphpora instance will be updated as follows:
[without health monitor]
backend 7d5d4323- f382-4a85- a965-4fcedd8c77 f2:199362ee- e305-4ebf- 947a-d3c155341a c9 6986-49c7- b46a-a17838d7a6 38 10.5.5.23:6443 weight 1 1f60-40d2- b748-d4e6be491e be 10.5.5.66:6443 weight 1
mode tcp
balance roundrobin
fullconn 50000
option allbackups
timeout connect 5000
timeout server 50000
server 91d6a444-
server 0e91354d-
[with TLS-HELLO health monitor]
backend 7d5d4323- f382-4a85- a965-4fcedd8c77 f2:199362ee- e305-4ebf- 947a-d3c155341a c9 6986-49c7- b46a-a17838d7a6 38 10.5.5.23:6443 weight 1 check inter 5s fall 3 rise 4 1f60-40d2- b748-d4e6be491e be 10.5.5.66:6443 weight 1 check inter 5s fall 3 rise 4
mode tcp
balance roundrobin
timeout check 10s
option ssl-hello-chk
fullconn 50000
option allbackups
timeout connect 5000
timeout server 50000
server 91d6a444-
server 0e91354d-