aledbf / kube-keepalived-vip

Kubernetes Virtual IP address/es using keepalived
Apache License 2.0
190 stars 75 forks source link

keepalived conf doesn't reload after deleted a pod #84

Closed patrickppeng closed 5 years ago

patrickppeng commented 5 years ago

I'm testing resilient with kube-keepalived-vip 0.30 by deleting the pod and I noticed the keepalived.conf didn't update the real_server IP with the new pod ip after k8s created the new pod. According to the README, I'm not sure what "scale event" keepalived is relied on to update and reload the conf. Did I miss anything or how to debug further with this issue?

kubectl version Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.1", GitCommit:"eec55b9ba98609a46fee712359c7b5b365bdd920", GitTreeState:"clean", BuildDate:"2018-12-13T10:39:04Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T17:53:03Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

WMP commented 5 years ago

I have this same on 0.32 version. I apply new configmap with new ip, and i want to reload keepalived, but i dont know how to do this.

aledbf commented 5 years ago

Closing. Please update to 0.33