The topology of the cluster is handled differently in the two deployment options (Classical and Containerized). The classical relies on a DigitalRoute developed application called System Topology Registry, while the containerized relies on Kubernetes (or other cluster management tool if ported). Note that classical deployments need a third party product in case high availability is a requirement, while containerized has this feature as part of Kubernetes.

Containerized MediationZone Deployments

Kubernetes (or other cluster management tool if ported), handles all aspects of cluster management of MediationZone:

• Creating, removing, starting, and stopping pico instances.
• Updating attributes of pico instances.
• Making all pico instances of the cluster highly available.
• Viewing cluster details.

For detailed user guides, please visit https://kubernetes.io/docs/home/managed by the System Topology Registry.

Classical MediationZone Deployments

...