Conversation
…on works (v1.3.3) Since #483 mounted haproxy.cfg directly from a ConfigMap, the container entrypoint (set_public_ip_and_start.sh) could no longer rewrite the config: ConfigMap volumes (and subPath file mounts) are always mounted read-only by the kubelet regardless of the readOnly flag, so its in-place sed -i 's/#PUBLIC_IP/tcp-request connection set-dst ipv4($PUBLIC_IP)/g' failed with 'Resource busy' / read-only filesystem. The #PUBLIC_IP placeholders were left untouched, HAProxy never set the destination address, and it advertised each pod's private IP to WhatsApp instead of the public egress IP (observed server-side as 'proxy IP address is unexpected: 10.0.x.x'). Fix, chart-only (no image rebuild): - Mount the ConfigMap read-only at a side path (/haproxy-config-src). - Mount a writable emptyDir at the canonical /usr/local/etc/haproxy. - An initContainer seeds the emptyDir with the image defaults (preserving errors/) and overlays the ConfigMap haproxy.cfg. The entrypoint can now edit haproxy.cfg in place at its normal location, so the config stays inspectable via the usual path and HAProxy advertises the real public IP again. Bump chart version to 1.3.3.
meta-cla
Bot
added
the
CLA Signed
jaltenmueller
approved these changes
Jun 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since #483 mounted haproxy.cfg directly from a ConfigMap, the container
entrypoint (set_public_ip_and_start.sh) could no longer rewrite the config:
ConfigMap volumes (and subPath file mounts) are always mounted read-only by
the kubelet regardless of the readOnly flag, so its in-place
failed with 'Resource busy' / read-only filesystem. The #PUBLIC_IP placeholders
were left untouched, HAProxy never set the destination address, and it
advertised each pod's private IP to WhatsApp instead of the public egress IP
(observed server-side as 'proxy IP address is unexpected: 10.0.x.x').
Fix, chart-only (no image rebuild):
errors/) and overlays the ConfigMap haproxy.cfg.
The entrypoint can now edit haproxy.cfg in place at its normal location, so the
config stays inspectable via the usual path and HAProxy advertises the real
public IP again. Bump chart version to 1.3.3.