EasyUC
English
Aurora

Choose appearance

Software, updates and licence files are available in the customer portal. Go to downloads

EasyUC platform

Structure, installation and operation of the EasyUC base system: Kubernetes, EasyUC Manager, nodes, updates, backup, certificates and ports.

Applies to: EasyUC 4.8.7 Last updated: October 2026

What the base system is

EasyUC is delivered as a virtual appliance and runs entirely in your data centre. There is an OVA for VMware vSphere/ESXi. Other hypervisors such as Proxmox, KVM or Hyper-V use the QCOW2 image or their own import.

Inside the appliance everything runs on Kubernetes, specifically on K3s with embedded etcd and an embedded registry. The first installation needs no internet access; all required files are part of the appliance.

You operate the platform through the EasyUC Manager at /manager. Its operator continuously reconciles the cluster with the desired configuration: version, modules and data services.

Delivery
OVA, QCOW2
Kubernetes
K3s with embedded etcd
Management
EasyUC Manager
Internet access
not needed for installation

Note

Each service runs as a single instance. Services affected by a node failure must restart. See Redundancy for the effects on operation and active calls.

Structure at a glance

Web traffic from users, agents and CUCM arrives via HTTPS at the Traefik ingress and is passed to the EasyUC components. acd-media and the Teams SBC run in the host network and accept their connections directly on the node.

The components use MariaDB, Elasticsearch and RabbitMQ, whose data lives on Longhorn volumes. Underneath, K3s runs on one or more Linux VMs. Details are in Architecture.

Layers of the EasyUC base system Six layers from top to bottom: clients and connected systems, Traefik ingress, EasyUC application components, data services, Longhorn and K3s. The EasyUC Manager in the easyuc-system namespace reconciles the application components and data services. 1 Clients and connected systems Users · agents · attendant consoles · CUCM · Microsoft Teams 2 Traefik ingress (HTTPS) /admin /enduser /agent /manager APIs /curri-api 3 EasyUC application components Kubernetes Deployments in the easyuc namespace 4 Data services MariaDB · Elasticsearch · RabbitMQ, each with its own operator 5 Longhorn Block storage for databases and files, replicated across nodes 6 K3s Control plane and embedded etcd on one or more Linux VMs EasyUC Manager API with operator easyuc-system reconciles continuously
Layers of the EasyUC base system. The EasyUC Manager controls application components and data services.

Topics

  • Architecture

    K3s, namespaces, data services and operators, components per module, ingress paths and storage.

  • EasyUC Manager

    Operator and custom resource, reconcile order and what you do in the Manager.

  • Redundancy

    etcd quorum, Longhorn replicas and what happens when a node fails.

  • Installation

    System requirements and the first steps from the OVA to the licence.

  • Adding nodes

    Requirements, procedure, etcd majorities and why three nodes.

  • Deployment types

    Module combinations such as CUCM + ACD or Teams + ACD and switching between them.

  • Updates

    Signed package file, procedure, interruption and the reset to the previous version.

  • Backup and restore

    Database backup and encrypted full backup, schedule, remote targets, restore and disaster recovery.

  • Certificates

    Web certificate via CSR and Teams SBC certificates from Let's Encrypt.

  • Ports and firewall

    Firewall reference: inbound, outbound and between nodes, filterable by module.