Avi Deitcher

Ideally, this should: 1. Receive request 2. Launch a function container to process it 3. Process 4. Terminate container upon completion of single request In practice, you do have cold-boot...

I think I still would keep the original router at a different layer. Users shouldn't need to think about routers, only about `event:function` maps. If you really want this to...

I have been struggling with this as well. Does the `docker_container` resource only support long-running containers? What would be the right way to run a one-shot command in docker and...

@clrxbl why does it matter? If you are bound to just 1 address, it will check the others, fail on those, but find the working one. The healthcheck will take...

This is a reasonable request. There are a few parts to this, though; it is a bit of a lift. * enabling BGP for ip6 at the project level *...

@flokli I just spent time going through that enhancement proposal. As far as I can tell, it looks like `loadBalancerIPs` will _not_ be implemented. I think that the simplest first...

> This could possibly be reduced to only metallb-system namespace. It cannot. We give the user the option to use the configmap in any namespace. Sure, most use it in...

I don't understand this. Why do we want to disable the node controller, and node labeling? The idea of the node controller being distinct from the services one is something...

Oh yes, now I remember. Just because I suggested it doesn't mean I would have any memory of it. I didn't love the approach, but it seemed the only possible...

This also came up in the CAPP/CPEM upgrade discussion (cc @detiber ). There are two distinct conversations going on here: * enabling some flexibility around what the provider ID should...