• Laurent Bernaille's avatar
    [kube-proxy/ipvs] Handle UDP graceful termination · ed65f6ed
    Laurent Bernaille authored
    The current logic is to delete a RS if the number of active connections
    is 0. This makes sense for TCP but for UDP the number of active
    connections is always 0. This is an issue for DNS queries because the RS
    will be deleted but the IPVS connection will remain until it expires
    (5mn by default) and if there are a lot of DNS queries, the port will be
    reused and queries blackholed. Of course for this to work properly the
    service needs to continue to serve queries until the connections expire
    (this works fine with the lameduck option of coredns).
    ed65f6ed
Name
Last commit
Last update
..
api Loading commit data...
apis Loading commit data...
auth Loading commit data...
capabilities Loading commit data...
client Loading commit data...
cloudprovider Loading commit data...
controller Loading commit data...
credentialprovider Loading commit data...
features Loading commit data...
fieldpath Loading commit data...
generated Loading commit data...
kubeapiserver Loading commit data...
kubectl Loading commit data...
kubelet Loading commit data...
kubemark Loading commit data...
master Loading commit data...
printers Loading commit data...
probe Loading commit data...
proxy Loading commit data...
quota Loading commit data...
registry Loading commit data...
routes Loading commit data...
scheduler Loading commit data...
security Loading commit data...
securitycontext Loading commit data...
serviceaccount Loading commit data...
ssh Loading commit data...
util Loading commit data...
version Loading commit data...
volume Loading commit data...
watch/json Loading commit data...
windows/service Loading commit data...
.import-restrictions Loading commit data...
BUILD Loading commit data...
OWNERS Loading commit data...
customers.yaml Loading commit data...