GitOps and the path to an autonomous core
To embed our video on your website copy and paste the code below:
<iframe src="https://www.youtube.com/embed/OBYFxRYK9M4?modestbranding=1&rel=0" width="970" height="546" frameborder="0" scrolling="auto" allowfullscreen></iframe>
Guy Daniels, TelecomTV (00:37):
Hello, you're watching TelecomTV and our special programme that looks at GitOps in a new light: the path to an autonomous core. I'm Guy Daniels, and today's discussion will examine how GitOps is changing the way telcos deploy, operate and manage their core networks, and why it could be a key step on the road to an autonomous core.
Josua Hiller, Swisscom (01:01):
For us, I would say the direction is very clear: we want to move towards an autonomous core. The reason is simple. Our networks are becoming more software-driven and more complex, and we cannot address that complexity simply by adding more operational effort. The important point is that the autonomy has to deliver business value as well. On this, we see three main benefits. Speed: bringing new capabilities and services to market faster. Efficiency: being able to manage growing complexity without growing operational effort at the same rate. And of course resiliency, where the network can increasingly detect deviations and recover safely. We also learned that cloud native alone doesn't make the network autonomous. A simple example is configuration. You can have a highly automated platform, but if some configuration data still sits, let's say, on an Excel sheet on an engineer's laptop, your automation stops there, and AI can't solve that for you either.
Abhishek Jaiswal, Ericsson (02:39):
We will evolve to a declarative, version-controlled state, which would mean faster, lower-risk changes and quicker revenue for the CSPs. Continuous GitOps brings a dimension of continuous reconciliation, as Josua pointed out, so a desired state will be continuously reconciled to the network, and drift will be automatically detected and corrected. This would mean fewer network incidents and fewer SLA penalties for the CSPs. And last but not least, with GitOps, Git becomes the single source of truth.
Josua Hiller, Swisscom (03:18):
We are seeing network function upgrades becoming two to three, or even four, times faster than before. Instead of large upgrades in dedicated maintenance windows, we can move towards smaller and more frequent changes. Today, I can proudly say we can perform fully automated changes during normal working hours, with our engineers on it within seconds if something fails. And the number of changes is completely different. On a very busy day, we are seeing around 20 changes going into our 5G network.
Caroline Chappell, CCSquared (04:04):
I think it's very clear from what Josua said that this is not just about technology; it's a change in processes and people too. GitOps is as much a cultural shift as a technical one. The most successful operators are those that address the organisational as well as the technical issues, and the least successful try to bolt new tooling on top of traditional team structures and processes.
Josua Hiller, Swisscom (04:28):
We've been on this journey for several years now and we are still learning. For me, that's an important message: you cannot simply introduce GitOps as a tool. You really have to transform the skills, the teams and the way of working around it. We also don't want AI simply pushing something into our live network. We need, let's say, a controlled path to production, so we can validate the change, test it in future against a digital twin, and then use GitOps to apply it in a consistent and traceable way. With continuous feedback, we can verify the results and react if something goes wrong. That's how I see the combination of AI, GitOps and the digital twin becoming the foundation for closed loops and then autonomous networks.
Caroline Chappell, CCSquared (05:45):
I think the most important thing, in terms of execution, is to get started. GitOps is so important, both to enable operators to realise 5G commercial goals and as a foundation for 6G, that they really can't afford to delay its adoption any longer.
Josua Hiller, Swisscom (06:03):
So my advice: start the journey, learn by doing, share your learnings and collaborate from the beginning.
Guy Daniels, TelecomTV (06:16):
For further information on the topics covered in this programme, please click and follow the links in the text below. For now though, thank you for watching, and goodbye.
Hello, you're watching TelecomTV and our special programme that looks at GitOps in a new light: the path to an autonomous core. I'm Guy Daniels, and today's discussion will examine how GitOps is changing the way telcos deploy, operate and manage their core networks, and why it could be a key step on the road to an autonomous core.
Josua Hiller, Swisscom (01:01):
For us, I would say the direction is very clear: we want to move towards an autonomous core. The reason is simple. Our networks are becoming more software-driven and more complex, and we cannot address that complexity simply by adding more operational effort. The important point is that the autonomy has to deliver business value as well. On this, we see three main benefits. Speed: bringing new capabilities and services to market faster. Efficiency: being able to manage growing complexity without growing operational effort at the same rate. And of course resiliency, where the network can increasingly detect deviations and recover safely. We also learned that cloud native alone doesn't make the network autonomous. A simple example is configuration. You can have a highly automated platform, but if some configuration data still sits, let's say, on an Excel sheet on an engineer's laptop, your automation stops there, and AI can't solve that for you either.
Abhishek Jaiswal, Ericsson (02:39):
We will evolve to a declarative, version-controlled state, which would mean faster, lower-risk changes and quicker revenue for the CSPs. Continuous GitOps brings a dimension of continuous reconciliation, as Josua pointed out, so a desired state will be continuously reconciled to the network, and drift will be automatically detected and corrected. This would mean fewer network incidents and fewer SLA penalties for the CSPs. And last but not least, with GitOps, Git becomes the single source of truth.
Josua Hiller, Swisscom (03:18):
We are seeing network function upgrades becoming two to three, or even four, times faster than before. Instead of large upgrades in dedicated maintenance windows, we can move towards smaller and more frequent changes. Today, I can proudly say we can perform fully automated changes during normal working hours, with our engineers on it within seconds if something fails. And the number of changes is completely different. On a very busy day, we are seeing around 20 changes going into our 5G network.
Caroline Chappell, CCSquared (04:04):
I think it's very clear from what Josua said that this is not just about technology; it's a change in processes and people too. GitOps is as much a cultural shift as a technical one. The most successful operators are those that address the organisational as well as the technical issues, and the least successful try to bolt new tooling on top of traditional team structures and processes.
Josua Hiller, Swisscom (04:28):
We've been on this journey for several years now and we are still learning. For me, that's an important message: you cannot simply introduce GitOps as a tool. You really have to transform the skills, the teams and the way of working around it. We also don't want AI simply pushing something into our live network. We need, let's say, a controlled path to production, so we can validate the change, test it in future against a digital twin, and then use GitOps to apply it in a consistent and traceable way. With continuous feedback, we can verify the results and react if something goes wrong. That's how I see the combination of AI, GitOps and the digital twin becoming the foundation for closed loops and then autonomous networks.
Caroline Chappell, CCSquared (05:45):
I think the most important thing, in terms of execution, is to get started. GitOps is so important, both to enable operators to realise 5G commercial goals and as a foundation for 6G, that they really can't afford to delay its adoption any longer.
Josua Hiller, Swisscom (06:03):
So my advice: start the journey, learn by doing, share your learnings and collaborate from the beginning.
Guy Daniels, TelecomTV (06:16):
For further information on the topics covered in this programme, please click and follow the links in the text below. For now though, thank you for watching, and goodbye.
Please note that video transcripts are provided for reference only – content may vary from the published video or contain inaccuracies.
Event highlights
Highlights from the Ericsson webinar ‘GitOps in a new light: The path to an autonomous core’, in which Abhishek Jaiswal of Ericsson, Caroline Chappell of CCSquared and Josua Hiller of Swisscom examine how GitOps is transforming core network deployment and operations, the role of continuous GitOps and declarative, version-controlled operations, the organisational and cultural change involved, how AI, GitOps and digital twins fit together, and much more.
Featuring:
- Abhishek Jaiswal, 5GC LCM Strategic Product Manager, Ericsson
- Caroline Chappell, Senior Analyst and Founder, CCSquared
- Josua Hiller, Director Mobile Core Services, Swisscom
Recorded: October 2026
For more information please visit Ericsson.com