Deepak Deore

@TaylorChristie similar issue with karpenter is being discussed at https://github.com/aws/karpenter-provider-aws/issues/4673 in your workaround karpenter removes node from LB during draining time --> then all pods get deleted but `karpenter-termination-waiter` daemonset...

> > > Interested to hear from contributors here whether the solution in #582, which adds the label `node.kubernetes.io/exclude-from-external-load-balancers` to nodes undergoing cordon-and-drain operations, is sufficient for your needs here....

> Hi @deepakdeore2004 and all, I'm writing here my findings after I was able to resolve the issue without any code changes. It might be helpful to other people. What...

thanks for the reply @Choms there may be typo in my repoduction steps but i ran same command with keepalive `off` but still see the keepalives ``` # vegeta --version...

> yeah, for that to work you need to change this line to be -1 instead of 0 https://github.com/tsenart/vegeta/blob/master/lib/attack.go#L188 > > then recompile Vegeta :) i see, then its a...

i am also getting same issue, waiting for the fix

someone mentioned workaround at https://github.com/aws/aws-node-termination-handler/issues/316#issuecomment-1970009212

after following https://my.f5.com/manage/s/article/K00026550 i can see keeplive on gateway with "netstat -panto" or "ss -pante" this is with bookinfo app exposed via istio gateway, the gateway shows keepalive which wasnt...

when is the next release scheduled to have Llama 3.1 and 3.2 tool use support?