The edge gateway has undergone several evolutions driven by changes in application architecture. Early gateways focused on load balancing and availability but evolved to support APIs and microservices. Adopting microservices and Kubernetes changes the architecture and development workflow, challenging edge management and requiring support for diverse workloads. There are three strategies for managing the edge with Kubernetes - deploying an additional gateway, extending an existing gateway, or deploying an in-cluster edge stack to simplify management. The optimal solution depends on the specific architecture and aims to scale edge management while supporting cloud-native practices.