1.13.2 HA 使用vip访问服务，间接性无法访问 about sealos HOT 4 CLOSED

你这感觉还不是k8s的锅， vip是keepalived提供的

from sealos.

keepalived日志

[root@master1 cat]# kubectl logs -f keepalived-master1 -n kube-system
2019-01-16 03:02:12,946 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
2019-01-16 03:02:13,098 INFO supervisord started with pid 1
2019-01-16 03:02:14,100 INFO spawned: 'keepalived' with pid 10
2019-01-16 03:02:14,180 INFO exited: keepalived (exit status 0; not expected)
2019-01-16 03:02:15,182 INFO spawned: 'keepalived' with pid 19
2019-01-16 03:02:15,186 INFO exited: keepalived (exit status 0; not expected)
2019-01-16 03:02:17,189 INFO spawned: 'keepalived' with pid 25
2019-01-16 03:02:17,195 INFO exited: keepalived (exit status 0; not expected)
2019-01-16 03:02:20,199 INFO spawned: 'keepalived' with pid 31
2019-01-16 03:02:20,207 INFO exited: keepalived (exit status 0; not expected)
2019-01-16 03:02:21,209 INFO gave up: keepalived entered FATAL state, too many start retries too quickly

[root@master1 cat]# kubectl logs -f keepalived-master2 -n kube-system
2019-01-16 03:02:14,858 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
2019-01-16 03:02:14,910 INFO supervisord started with pid 1
2019-01-16 03:02:15,912 INFO spawned: 'keepalived' with pid 8
2019-01-16 03:02:15,966 INFO exited: keepalived (exit status 0; not expected)
2019-01-16 03:02:16,967 INFO spawned: 'keepalived' with pid 17
2019-01-16 03:02:17,985 INFO success: keepalived entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-01-16 03:02:17,985 INFO exited: keepalived (exit status 0; expected)

from sealos.

这keepalived是凉了的节奏啊 keepalived进程应该停了吧

from sealos.

已经更新了keepalived镜像，可以使用fanux/sealos:1.13.2试试

from sealos.