Demonstrate how to addressing the limitations of Visual Studio Bridge to Kubernetes with the power of Cilium L7 Network Policy and custom tunnel agent.
is important • How Cilium L7 Network Policy works • Imporve Development Experience with Cilium • What is Bridge To Kubernetes and its limitations • How to customize Cilium L7 Network Policy to address the Bridge To Kubernetes limitations Outline
restart pods • ONLY traffic matched by L4 level policy is processed • Do whatever you want to the traffic, ex: • HTTP access control • RPC redirection • DB connection mutation, auditing FULL control of L7 traffic With Golang Envoy Filter
• Need to re-deploy container to reflect code changes • For Debugging: • Hard to target traffic to the which remote container • Hard to inspect the memory of the remote container (maybe uprobe) Microservice Development Experience Some Pain Points
to L7 traffic • Visual Studio Bridge To Kubernetes • Improve microservice development experience • Build your own Bridge To Kubernetes with Cilium • Addressing the BTK limitations • Full Code of Tunnel and Golang Envoy Filter: • http://github.com/rueian/aerial • https://github.com/rueian/cilium/tree/httpredirect Recap