The Netcup failover watchdog analyses your swarm cluster and can redirect your failover to that server, that currently runs a specific container (e.g. your Nginx Ingress). This ensures that in case of failure, your failover ip gets automatically redirected as well as that your traffic does not take any unnecessary routes through your ingress mesh.
version: '3.8'
services:
app:
image: fbieringer/netcup_failover
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
deploy:
placement:
constraints:
- node.role == manager
environment:
login: 12345 # Your netcup user id
password: This password has to be generated in your SCP and is NOT your normal netcup password
ip: "123.123.123.123" # IP for your failover
service: "test_web" # Name of the docker swarm service that should be watched
# [docker_node_name] [netcup_server_name] [mac_adress of interface]
servers: |
srv1 v12345467890001 00:11:22:33:44:55
srv2 v12345467890002 00:11:22:33:44:66
# optional mask, if you map a subnet not an ip
# mask: 32
# optional timeout in seconds between checks of the service
# timeout: 5
Content type
Image
Digest
sha256:18df53511…
Size
41.8 MB
Last updated
about 3 years ago
docker pull fbieringer/netcup_failover