Turning platform migration guidance into an automated risk report
The problem
Many organisations run their applications on an internal developer platform built on top of a public cloud and Kubernetes. The platform gives product teams a paved road: clusters, networking, ingress, monitoring, and security scanning out of the box.
Sooner or later, that platform needs a new generation. When it arrives, every product has to move, and the old platform gets a fixed shutdown date. Teams have to migrate while still shipping features.
A typical next-generation platform changes how teams own, configure, and secure their workloads:
Area Old platform New platform
Cloud account A resource group per team A dedicated cloud subscription per team, with more control
Management A YAML configuration file in each repo A self-service portal
Network & security One shared network Redesigned network; outgoing traffic can be restricted per namespace
Ingress ingress-nginx Traefik, since ingress-nginx has been retired by theβ¦