Steven Sheehy

--bind_ip_all will require mongodb 3.6 or later. --bind_ip=0.0.0.0 accomplishes the same thing and is backwards compatible with earlier versions.

I have something working locally that splits the summary into request and response summaries with count, rate, size and speed. I haven't had time to complete it. ``` Request Summary:...

@murali-reddy I've solved this manually with a script I wrote. It routes all outgoing pod traffic that is not to another pod or service to the VIP and SNATs it...

@murali-reddy Yes, it is a single layer-2 VIP created by kube-keepalived-vip and used as an ExternalIP on each service. So single VIP for all nodes, but only one machine at...

@murali-reddy I've refactored it and packaged our egress script into a reusable daemonset and opened source it as [kube-egress](https://github.com/steven-sheehy/kube-egress). It works for our needs but probably for most people it's...

@murali-reddy If you mean the pod subnet specifically for that node allocated by the CNI, then yes that works correctly. I use the overall cluster pod subnet and only use...

Please note that if approved, going forward the chart version should be bumped before a tag if there were any chart changes in that release.

Not sure what you mean. It looks to me like it starts at 18:29:22.083291 and then two seconds later at 18:29:24.154581 it reloads the keepalived configuration and begins sending gratuitous...

Please try with latest version.

That's simply not possible to use kube-keepalived-vip as the VIP for the apiserver. This is like you said a chicken and egg problem since the apiserver depends upon kube-keepalived-vip for...