Enable endpoint-mode dnsrr for traefik itself
#52
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
#50 (comment)
/cc @mirsal
AFAIU we need to repeat the change from the previous PR but then for the
traefikservice?nope, not while ports are exposed using the ingress routing mesh (which is useless in single-server deployments btw).
it can be done in
compose.host.ymlthoughArgh, sorry, I'm just not sure what change to make altho I've read everything in #50 5 times 😅
If you have time for a PR, then I'll get on a review again?
@p4u1 do you have any understanding of how to resolve this? i would like to see if there are any performance gains we can win back from this change.... the saga begins with #52 (comment)
I didn't read everything but from my understanding it makes sense to change:
This will be a breaking change though and we should test it for a while
@Apfelwurm what do you think?
Bypassing the ingress routing mesh (which is actually implemented as a hidden haproxy container) will shave a few milliseconds of latency off every ingress request, but more important than performance, host mode port publishing for traefik would give us IPv6 ingress
After reading in the topic again again (thanks @mirsal for #50 (comment) , never read one single message that told me more about docker internals that i did not know before! Swarm is pretty new to me :D Strong one, cleared up so much in my head about stuff i recently saw that i could not explain till now!) my take on this would be similar to your propsal @p4u1:
compose.host.ymlto our defaultcompose.ymland empty it out, so the upgrade deploy does not break when people have it enabled in their envs (or is this maybe already handled in abra? :D)dnsrrmodeto traefik incompose.ymlcompose.no-host.ymlthat overwritesendpoint-modetovipand themodeof theports 80/443 toingressSince this might be really bad for the one person that most likeley has any special setup, that breaks by this change in default behaviour, maybe we ask again in matrix (this might be something for the non tech channel, even though its deeply tech), if someone is running multiple traefik instances on one server or at least announce that we plan this breaking change?