Cloud

Featured image by Pexels: https://www.pexels.com/photo/cloudy-sky-531756/

Those who pay attention and follow the 5G space have probably noticed the phenomenon of Operators moving their infrastructure over to the cloud providers.

We introduce Cilium, an open source community-driven project that aims to drive software-driven networking, network observability, and monitoring for cloud-native microservice-based deployments on Kubernetes and other container orchestration platforms.

As service providers begin to roll out 5G POCs and initial deployments, there is no question that these cloud native platforms will be huge Capex and Opex investments on their part. These platforms should be able to handle diverse workloads such as telco, edge and enterprise applications. They must be efficient as well as robust from an operational standpoint. They must also serve the operator well for years. While it is never my intention to be hyperbolic or combative, the question is if Openstack is a viable 5G platform – when compared with hyperscaler clouds.

Using the above architecture and dataflow model, eBPF programs can be attached to key ingress and egress points when the kernel processes networking packets. That leads us to SDN, monitoring, tracing et al.

This post is an introduction to eBPF where we will discuss the key capabilities Solutions Architects and Technology Managers should look for. We will follow up with a deep-dive around individual capabilities in the following posts.

For most production deployments, the 5G core should be deployed on a hyperscale cloud provider. This is to ensure scalability and dynamic orchestration of network resources over an infinitely scalable base. This blog post covers the key reasons to do so.

s telcos and other CSPs begin moving to 5G RAN and 5G Core deployments, these are overwhelmingly based on Cloud-native microservice architectures, REST APIs, Kubernetes-based containers, and NoSQL databases for stateless architecture are commonly implemented in telecom networks. With this blog, we begin discussing life cycle management of 5G networks.

Prior to the advent of K8s and Cloud-Native functions, network functions (NFs) were primarily deployed by CSPs as a combination of physical appliances and some VMs.

As we discuss in this blog, Karpenter observes events within the Kubernetes cluster, and then sends provisioning commands to resources in the underlying cloud provider.