kfox1111

For external clients though, this means your clients need to be either pointed at coredns or your coredns is hung off of the greater DNS system? If thats the case,...

I think its probably fine to load balance the apiserver endpoint using metallb managed within the cluster. You just need to separate the use cases: 1. kubelet -> apiserver on...

@liuyuan10 interesting issue. Wouldn't that happen for non k8s services too? Is this a bigger problem for Metallb in general, not just using it to front kube-apiserver? Separate but related...

Is there something metallb could do to help? Its already arping the ip. There something reasonable it could do on failover to send fin packets out? Or is there not...

Yes, but I don't see how keepalived + haproxy failing over to another node doesn't have the same problem with the kubectl client talking to the vip / haproxy when...

I don't understand how. Does keepalived keep track of connections so it can send out tcp fin's for the failed node? If kubectl connects to vip. the node with vip...

I think its a passive thing though, right? The client must send a packet to the node that was failed over to, before the kernel there notices that the connection...

Looking to do the same. Will look into a shell wrapper for now. Does anyone have a singularity wrapper already and willing to share? :)

I have not gotten a chance to look at funnel further. But in general, Singularity is working pretty well on our HPC clusters. Recently I've started using podman/buildah on my...

Podman takes those same arguments and works in rootless mode. Making the command executed configurable so that s/docker/podman/ can be ran would be interesting.