+1 NB I especially appreciate the componentized nature of flux 2 and how it leads to adapting to all sorts of interesting situations that go beyond the initial use cases. Excited to see the project co

Repeating my +1 NB here. So glad to see this happening. Joe

Sorry for being late to the party here. +1 NB Clearly I’m biased here because I helped get SPIFFE going. But I think this is a critical part of our emerging cloud native toolkit and I’m excited but he

I want to echo my support for this effort. Thank you for introducing it, Paris. Setting community standards and enforcing them is a key part of making our ecosystem work and I believe it is critical t

Personally I disagree that this is akin to asking for a license change. The name is an intrinsic part of the project. It is the primary key for the community. This feels more like accepting a fork (we

IC4E only begs the question about what it stands for. It also doesn't set the project up, IMO, for success as the more memorable name will be with the commercial entity and it could stunt the developm

What is the new name? The name "ambassador" is all over the docs and I'd expect to see this reframed around the new name. I object to the name "Ingress Controller for Envoy Proxy” as that also describ

+1 binding

Awesome! Congrats to the project and the team. Thanks for the update Phil!

+1 (non-binding) I've been talking with Matt and Envoy is a great piece of tech!