badblocks/docker-easy-haproxy
1
0
Fork 0
Code Activity

Fix English

Browse source
This commit is contained in:
Joao M 2022-09-01 16:42:46 +00:00
parent 19df0414c0
commit 483bb9a55e
10 changed files with 82 additions and 71 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/limitations.md
View file

@ -2,15 +2,12 @@
EasyHAProxy currently expects to work in a single replica.
If more than one replica is running, EasyHAProxy will continue to work, however each replica will discover
the services independently.
If more than one replica is running, EasyHAProxy will continue to work. However, each replica will discover the services independently.
It means replicas can be out-of-sync for a few seconds because each replica will discover the pods
separately.
It means replicas can be out-of-sync for a few seconds because each replica will discover the pods separately.
For Letsencrypt this is worse because each replica will a Letsencrypt certificate and can fail because the
letsencrypt challenge can be directed to the other replica. Also, you can hit the certificate issue limit.
So if you intend to run multiple replicas **do not** activate letsencrypt.
For Letsencrypt, this is worse because each replica will have a Letsencrypt certificate, and issuing a new one can fail because the
letsencrypt challenge can be directed to the other replica. Also, you can hit the certificate issue limit. So if you intend to run multiple replicas **do not** activate letsencrypt.
----
[Open source ByJG](http://opensource.byjg.com)