Getting Started
Overview
The AgileTV CDN Manager (product code ESB3027) is a cloud-native control plane for managing CDN deployments. It provides centralized orchestration for authentication, configuration, routing, and metrics collection across CDN infrastructure.
Before You Start:
- Deployment type: Lab (single-node) or Production (multi-node)? See Installation Guide
- Hardware: Nodes meeting specifications for your deployment type
- OS: RHEL 9.4 or later, or a compatible clone (Oracle Linux, AlmaLinux, Rocky Linux)
- Software: Installation ISO from AgileTV customer portal
- Network: A default route on every node and, optional but recommended, a backplane network for node-to-node traffic, separate from the public network. See the Networking Guide
Deployment Models
| Deployment Model | Description | Typical Use Case |
|---|---|---|
| Self-Hosted | K3s Kubernetes cluster on customer premises | Production deployments |
| Lab/Single-Node | Minimal single-node installation | Acceptance testing, demonstrations, development |
Functionality remains consistent across deployment models.
Prerequisites
- Installation ISO: Obtain
esb3027-cdn-manager-X.Y.Z.isofrom AgileTV customer portal - OS: RHEL 9.4 or later, or a compatible clone (Oracle Linux, AlmaLinux, Rocky Linux)
- Kubernetes familiarity: Basic understanding of pods and deployments helps with troubleshooting
For detailed hardware, network, and operating system requirements, see the System Requirements Guide.
Installation
Ready to install? The Quickstart takes three freshly installed machines to a working cluster, step by step, with the deploy command on the installation ISO. The Installation Guide covers the details and variations, including single-node labs.
Accessing the System
Following successful deployment, the following interfaces are available:
| Service | URL Path | Authentication |
|---|---|---|
| MIB Frontend | /gui | Zitadel SSO |
| API Gateway | /api | Bearer token |
| Zitadel Console | /ui/console | See Glossary |
| Grafana | /grafana | See Glossary |
All services are accessed via https://<cluster-host><path>.
Important:
<cluster-host>must be the main manager hostname, the first entry ofmanager_hostnamesin the site settings. Pages may load under another name, but signing in only works using the configured hostname. To reach the system by IP address, configure that IP address at installation time.
Note: Without a TLS certificate of your own, a temporary self-signed certificate is served, and browsers show a warning. For production deployments, install a certificate from a trusted certificate authority before exposing the system to users. See TLS Certificates.
Initial user configuration is performed through Zitadel. See Next Steps for securing the administrator account and adding users. For detailed guidance on managing users, roles, and permissions in the Zitadel Console, see Zitadel’s User Management Documentation.
Documentation Navigation
The following guides provide detailed information for specific operational tasks:
| Guide | Description |
|---|---|
| System Requirements | Hardware, operating system, and network specifications |
| Architecture | Detailed system architecture and scaling guidance |
| Installation | Step-by-step installation and upgrade procedures |
| Configuration | System configuration and customization |
| Performance Tuning | Optimization tips for improved performance |
| API Guide | REST API reference and integration examples |
| Operations | Day-to-day operational procedures |
| Metrics & Monitoring | Monitoring dashboards and alerting configuration |
| Troubleshooting | Common issues and resolution procedures |
| Glossary | Definitions of technical terms |
| Release Notes | Version-specific changes and known issues |