Idk how I missed eBPF ( horrible name btw ). Cilium seems to be the bread winner in the family now.
My previous experience was in Consual + Envoy. And now the project is moving into the direction of Nginx Fabric.
I wish this stack would’ve been more widely communicated and thought.
My previous experience was in Consual + Envoy. And now the project is moving into the direction of Nginx Fabric.
I wish this stack would’ve been more widely communicated and thought.
January 30, 2025 at 12:29 AM
Idk how I missed eBPF ( horrible name btw ). Cilium seems to be the bread winner in the family now.
My previous experience was in Consual + Envoy. And now the project is moving into the direction of Nginx Fabric.
I wish this stack would’ve been more widely communicated and thought.
My previous experience was in Consual + Envoy. And now the project is moving into the direction of Nginx Fabric.
I wish this stack would’ve been more widely communicated and thought.
Well gateway was obvious, but I never would guessed that you can configure envoy to support peer to peer communication without central data plane. Super cool hack
January 30, 2025 at 12:08 AM
Well gateway was obvious, but I never would guessed that you can configure envoy to support peer to peer communication without central data plane. Super cool hack
Gateway and Service mesh were always coupled together for me. In any job it was always a construct of the ever increasing rush. Now I got some time to slow down, it is super interesting to learn that apparently you can do either.
January 30, 2025 at 12:08 AM
Gateway and Service mesh were always coupled together for me. In any job it was always a construct of the ever increasing rush. Now I got some time to slow down, it is super interesting to learn that apparently you can do either.