Managing Legacy to Cloud Native with GitOps at Deutsche Telekom
summary
Deutsche Telekom migrates 5G network functions from siloed VMs to a disaggregated cloud native stack using GitOps with Flux-based reconciliation, converting desired state in Git into running state via CI/CD pipelines and doing multiple smaller releases per week instead of annual upgrades. They build hybrid Telco+Cloud teams, add non-stop testing in production, and centralize telemetry for AI Ops root-cause automation. Rolling upgrades still risk minutes of downtime versus legacy yearly SLAs, so progressive delivery and canary strategies are essential.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:36Agenda
- 1:17Why Cloud Native
- 4:21De disaggregation
- 6:25Legacy vs Cloud Native
- 7:56Reconciliation
- 8:52Automation for reconciliation
- 9:38Avoiding vendorspecific network element managers
- 11:02Introducing Cloud Native New Mindset
- 12:30Core Competences
- 13:59Life Cycle Management
- 14:50Challenges
- 16:07Butterfly Effect
- 18:10Conclusions
related talks
30mDevOps: Supporting aircraft from hanger to take-off
26mDevOps and Lean in Legacy Environments
23mDevOps and Legacy Code
29mBringing New Technology to Legacy Land - Don Fossgreen, Thomas Squeo (West)
18mUnlocking Value from Legacy Technology
05mBalancing Technical Debt and Modernisation in DevOps
58mJourney to the Cloud - a Rearchitecting Story
18mMigrating Legacy Financial Systems to Cloud: Challenges and Best Practices