Traffic routing |
Interlock uses back-end task IPs to route traffic from the
proxy to each container. Traffic to the front-end route is layer 7 load
balanced directly to service tasks. This allows for routing
functionality such as sticky sessions for each container. Task routing
mode applies layer 7 routing and then sends packets directly to a
container. |
Interlock uses the Swarm service VIP as the back-end IP instead of
using container IPs. Traffic to the front-end route is layer 7 load
balanced to the Swarm service VIP, which Layer 4 load balances to
back-end tasks. VIP mode is useful for reducing the amount of churn in
Interlock proxy service configurations, which can be an advantage in
highly dynamic environments.
VIP mode optimizes for fewer proxy updates with the tradeoff of a
reduced feature set. Most application updates do not require configuring
back ends in VIP mode. In VIP routing mode, Interlock uses the service
VIP, which is a persistent endpoint that exists from service creation to
service deletion, as the proxy back end. VIP routing mode applies Layer
7 routing and then sends packets to the Swarm Layer 4 load balancer,
which routes traffic to service containers.
|
|---|
Canary deployments |
In task mode, a canary service with one task next to an existing service
with four tasks represents one out of five total tasks, so the canary
will receive 20% of incoming requests. |
Because VIP mode routes by service IP rather than by task IP, it affects
the behavior of canary deployments. In VIP mode, a canary service with
one task next to an existing service with four tasks will receive 50%
of incoming requests, as it represents one out of two total services. |
|---|