Getting Started

Introduction to AgileTV CDN Manager
You're viewing a development version of manager, the latest released version is 1.6.2
Go to the latest released version

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 ModelDescriptionTypical Use Case
Self-HostedK3s Kubernetes cluster on customer premisesProduction deployments
Lab/Single-NodeMinimal single-node installationAcceptance testing, demonstrations, development

Functionality remains consistent across deployment models.

Prerequisites

  • Installation ISO: Obtain esb3027-cdn-manager-X.Y.Z.iso from 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:

ServiceURL PathAuthentication
MIB Frontend/guiZitadel SSO
API Gateway/apiBearer token
Zitadel Console/ui/consoleSee Glossary
Grafana/grafanaSee Glossary

All services are accessed via https://<cluster-host><path>.

Important: <cluster-host> must be the main manager hostname, the first entry of manager_hostnames in 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:

GuideDescription
System RequirementsHardware, operating system, and network specifications
ArchitectureDetailed system architecture and scaling guidance
InstallationStep-by-step installation and upgrade procedures
ConfigurationSystem configuration and customization
Performance TuningOptimization tips for improved performance
API GuideREST API reference and integration examples
OperationsDay-to-day operational procedures
Metrics & MonitoringMonitoring dashboards and alerting configuration
TroubleshootingCommon issues and resolution procedures
GlossaryDefinitions of technical terms
Release NotesVersion-specific changes and known issues