On our journey to highly flexible, sustainable, and resilient networks for the future, we believe in applying the following cloud native principles to all layers of network infrastructure, applications, and services*:
1. Decoupled infrastructure and application lifecycles over vertical monoliths;
2. ‘API first’ over manual provisioning of network resources;
3. Declarative and intent-based automation over imperative workflows;
4. GitOps** principles over traditional network operations practices;
5. Unified Kubernetes (or the like) resource consumption patterns over domain-specific resource controllers;
6. Unified Kubernetes (or the like) closed-loop reconciliation patterns over vendorspecific element management practices; and
7. Interoperability by well-defined certification processes over vendor-specific optimisation.
We also believe that openness and compatibility principles need to be key drivers of future Telecom and network services implementations to ensure we leverage Cloud Native principles to encourage software – orchestration – and hardware disaggregation.
Building a cloud native architecture calls for a joint effort among telecom operators, suppliers, and partners. This is described in this document by stating a few principal requirements and by outlining the area of focus for this journey from an operator point of view.
* Does not imply order of priority
** Everything as code, single point of truth, immutable source of trust