Open sdayvz opened 5 hours ago
Hi, I use vip-manager 2.8.0 and consul 1.19.0 When I stopped the vip-manager service, the VIP still assigned on server. I can see the VIP like this:
2: ens224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:50:56:b0:0a:a1 brd ff:ff:ff:ff:ff:ff altname enp19s0 inet 10.10.10.10/24 brd 10.88.0.255 scope global noprefixroute ens224 valid_lft forever preferred_lft forever inet 10.10.10.11/24 scope global secondary ens224 valid_lft forever preferred_lft forever
Here is the vip-manager settings:
interval: 1000 trigger-key: "/patroni/dengage/leader" trigger-value: "dengage-01" ip: 10.10.10.11 netmask: 24 interface: ens224 hosting-type: basic dcs-type: consul dcs-endpoints: - http://127.0.0.1:8500 consul-token: "f62e9800-282a-2baa-5564-71a79f87092e" retry-num: 2 retry-after: 250 #in milliseconds verbose: false
Is this a bug? If not, is there a setting to delete VIP automatically? Thanks.
Hi, I use vip-manager 2.8.0 and consul 1.19.0 When I stopped the vip-manager service, the VIP still assigned on server. I can see the VIP like this:
Here is the vip-manager settings:
Is this a bug? If not, is there a setting to delete VIP automatically? Thanks.