telco-hub-pattern/
├── kustomize/overlays/telco-hub/ # 🔧 Kustomize Overlay Configuration
│ └── kustomization.yaml # Component selection and patches
├── kustomize/air-gapped/ # 🛡️ Disconnected (air-gapped) assets
│ ├── imageset-config.yaml # Image mirroring (oc-mirror)
│ ├── prerequisites/ # Cluster proxy, catalogs, CAs
│ │ └── kustomization.yaml
│ └── README.md # Disconnected deployment guide
├── values-hub.yaml # Hub Cluster Definition
├── values-global.yaml # Global Pattern Settings
└── docs/ # Documentation
# Consumed Remote Resources (via kustomize):
# https://github.com/openshift-kni/telco-reference/tree/main/telco-hub/configuration/reference-crs/
├── required/ # 🔧 Essential Components
│ ├── acm/ # Advanced Cluster Management
│ ├── gitops/ # GitOps Operators & Configuration
│ ├── talm/ # Topology Aware Lifecycle Manager
│ └── registry/ # Local Registry (disconnected)
└── optional/ # 🔌 Optional Components
├── lso/ # Local Storage Operator
├── odf-internal/ # OpenShift Data Foundation
└── logging/ # Cluster Logging StackTelco Hub
Validation status:
SandboxCI status:
Links:
About the Telco Hub pattern
The Telco Hub pattern is a GitOps-first validated pattern for deploying and operating a Telco-focused management hub on Red Hat OpenShift Container Platform. It uses a GitOps approach to centralize multi-cluster operations, lifecycle management, and policy enforcement to simplify the deployment and Day 2 operations of Telco workloads and edge clusters.
When the pattern installation is complete, the hub cluster provides:
A dedicated GitOps (ArgoCD) instance created to manage spoke clusters. This instance includes resource tuning for scalability and an ACM plugin for simplified creation of policies.
Support for Zero Touch Provisioning (ZTP) workflows, which provide automated cluster installation and configuration.
The Topology Aware Lifecycle Manager (TALM) for integrated cluster management and upgrade capabilities.
Centralized management of distributed telco infrastructure.
Background
Telco networks and cloud-native network functions (CNFs) require fast, repeatable lifecycle operations, strict dependency management, and consistent configuration across many clusters and edge sites. This pattern packages a production-ready, GitOps-based hub that uses validated upstream telco-reference CRs and applies environment-specific Kustomize overlays so Operators deploy and manage Telco platforms consistently.
Use Cases
Telco Edge Hub Management: Deploy and manage multiple edge clusters from a central hub
Zero Touch Provisioning: Automated cluster installation and configuration via ZTP workflow
Multi-Cluster Operations: Centralized management of distributed telco infrastructure
GitOps Workflows: Infrastructure-as-code with automated deployment and synchronization
Red Hat technologies
Red Hat OpenShift Container Platform
Red Hat Advanced Cluster Management (RHACM)
Red Hat OpenShift GitOps (ArgoCD)
Topology Aware Lifecycle Manager (TALM)
Optional: Local Storage Operator (LSO)
Optional: Red Hat OpenShift Data Foundation (ODF)
Optional: Red Hat Cluster Logging Operator (CLO)
Other technologies
Support for disconnected (air-gapped) environments through local registries, cluster proxy configuration, and image mirroring (
ImageSetConfiguration).A dedicated GitOps (ArgoCD) instance that includes resource tuning for scalability and an ACM plugin for simplified creation of policies for managed clusters.
Architecture
The Telco Hub pattern architecture consists of the following key components:
- Design principles
Principle | Description | Benefit |
Reference-based | Direct consumption of official telco-reference configurations | Always use validated, upstream telco designs |
GitOps-Native | ArgoCD manages all deployments via validated patterns framework | Automated, auditable infrastructure changes |
Kustomize-First | Environment-specific overlays without modifying upstream configs | Customize while maintaining upstream compatibility |
Component Selection | Declarative component enablement via kustomize resources | Granular control over telco-hub functionality |
