aee9645b43
Verified against source code and enhanced with Docusaurus markdown features: Documentation Accuracy Fixes: - Fixed acme.md: Added "letsencrypt" as valid AUTOCONFIG value (was incorrectly shown as "-") - Added reference to ACME docs from environment-variable.md - Verified all features against actual implementation in /src Docusaurus Enhancements Added: - Admonitions (:::note, :::tip, :::warning, :::danger, :::info) for important callouts - Code block titles for all bash/yaml examples (e.g., title="Install EasyHAProxy") - Better structured warnings and notes for limitations - Improved formatting and readability throughout Files Enhanced: - kubernetes.md: Added info boxes, warnings, code titles - docker.md: Added limitation warnings, code titles - swarm.md: Added advantage tips, limitation warnings - acme.md: Fixed Let's Encrypt autoconfig, enhanced requirements with admonitions - ssl.md: Added code block titles for all examples - static.md: Added live reload tip, SSL certificate note - container-labels.md: Added definition explanation, code titles - limitations.md: Restructured with clear warnings and explanations - helm.md: Added warnings, code titles - microk8s.md: Added ingress controller warning, code titles - volumes.md: Added info box about volume purposes - other.md: Added code block titles - environment-variable.md: Added ACME reference note All changes verified against actual Python source code implementation.
38 lines
No EOL
1.6 KiB
Markdown
38 lines
No EOL
1.6 KiB
Markdown
---
|
|
sidebar_position: 15
|
|
---
|
|
|
|
# Limitations and Considerations
|
|
|
|
## EasyHAProxy will not work with --network=host
|
|
|
|
:::danger Network Mode Incompatibility
|
|
The `--network=host` option **cannot** be used with EasyHAProxy due to its networking requirements.
|
|
|
|
EasyHAProxy needs to inspect and interact with Docker containers from within the Docker network where it's running. Using the `--network=host` option bypasses Docker networking, preventing EasyHAProxy from accessing and configuring containers effectively.
|
|
:::
|
|
|
|
## Considerations for Multiple Replica Deployments in EasyHAProxy
|
|
|
|
:::warning Single Replica Deployment Recommended
|
|
EasyHAProxy is designed for single replica deployment.
|
|
:::
|
|
|
|
### What happens with multiple replicas?
|
|
|
|
EasyHAProxy can still operate with multiple replicas; however:
|
|
|
|
1. **Service Discovery**: Each replica will independently discover services, which may lead to temporary inconsistencies among replicas (out-of-sync for a few seconds).
|
|
|
|
2. **ACME/Certificate Issues**: Running multiple replicas creates significant problems with Let's Encrypt and other ACME certificate issuance:
|
|
- Each replica will attempt to obtain its own certificate
|
|
- ACME challenges may be directed to different replicas, causing failures
|
|
- You may quickly hit certificate issuance rate limits
|
|
- Certificate renewal may fail unpredictably
|
|
|
|
:::danger Recommendation
|
|
If you need to run multiple replicas for high availability, **do not activate ACME/Let's Encrypt**. Instead, use manually managed certificates or an external certificate management solution.
|
|
:::
|
|
|
|
----
|
|
[Open source ByJG](http://opensource.byjg.com) |