Oct 28, 2026 · 1 hr 2 min · 11 segments
Eric Chou is joined by Mauricio Rojas, Principal DevOps Consulting Engineer at Nokia, to unpack how the stack of Kubernetes, GitOps, and open-source tooling can fundamentally transform modern…
Eric ChouHost
Yeah, so is it the main point to have a quote-unquote smaller scale of digital twin of your production for learning, for prototyping, or is it actually have some sort of tie into production as well? I'm asking because I think it's pretty obvious that the connection between your role, like demo and learning and all of that with this stack that you just have to, you could spin up with like a make, right? But is there any other tie-in for production besides just trying things out and doing prototyping?
Well, we expect this to be used on production because this is the reason that we put it on Kubernetes and not just using Docker Compose.
And we try to make it very portable to just put it in any sort of Kubernetes cluster.
You don't need to have just one dedicated instance for just one specific topology or domain.
For example, you can use the same solution for more than one BNG domain or for more than a different domain like a BNG or direct internet access if you have other kinds of services.
then we are trying to make this in Kubernetes to make it ready for production.
The playground is for you to just try it, but you have the Kubernetes packages that you can use and take those directly to any sort of Kubernetes with more nodes that is going to give you more resilience or scale.

So maybe for somebody who is outside of a service provider domain, I have to look it up.

And so maybe you could tell us a little bit about BNG and what it is, what's a high-level function that it serves, and why you choose to use it in your lab.
It's natural if you're working on the data center, you're going to start learning new things in the service provider.
For example, when I was working very tight on the data center business with other solutions here at Nokia, I didn't know so much about different use cases that you have in the service providers.

Yeah, so is it the main point to have a quote-unquote smaller scale of digital twin of your production for learning, for prototyping, or is it actually have some sort of tie into production as well? I'm asking because I think it's pretty obvious that the connection between your role, like demo and learning and all of that with this stack that you just have to, you could spin up with like a make, right? But is there any other tie-in for production besides just trying things out and doing prototyping?
Well, we expect this to be used on production because this is the reason that we put it on Kubernetes and not just using Docker Compose.
And we try to make it very portable to just put it in any sort of Kubernetes cluster.
You don't need to have just one dedicated instance for just one specific topology or domain.
For example, you can use the same solution for more than one BNG domain or for more than a different domain like a BNG or direct internet access if you have other kinds of services.
then we are trying to make this in Kubernetes to make it ready for production.
The playground is for you to just try it, but you have the Kubernetes packages that you can use and take those directly to any sort of Kubernetes with more nodes that is going to give you more resilience or scale.

So maybe for somebody who is outside of a service provider domain, I have to look it up.

And so maybe you could tell us a little bit about BNG and what it is, what's a high-level function that it serves, and why you choose to use it in your lab.
It's natural if you're working on the data center, you're going to start learning new things in the service provider.
For example, when I was working very tight on the data center business with other solutions here at Nokia, I didn't know so much about different use cases that you have in the service providers.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.