Refactoring applications into microservices and Kubernetes brings new challenges for managing the edge, particularly with multiple configurations to manage for various microservices. To address this, three strategies can be employed: deploying an additional API gateway, extending an existing API gateway, or deploying a comprehensive self-service edge stack. Each strategy has its pros and cons, including varying degrees of change required, management overhead, and operational complexity. By understanding these trade-offs, organizations can choose the best approach to manage their APIs and edge in a microservices-based architecture deployed into Kubernetes clusters.