Zerto in Kubernetes Environments
Zerto helps customers accelerate IT transformation through a single, scalable platform for cloud data management and protection. Built for enterprise scale, Zerto’s simple, software-only platform uses continuous data protection to converge disaster recovery, backup, and data mobility and eliminate the risks and complexity of modernization and cloud adoption. Zerto enables an always-on customer experience by simplifying the protection, recovery, and mobility of applications and data across private, public, and hybrid clouds. Zerto is trusted by over 9,500 customers globally and is powering offerings for Microsoft Azure, IBM Cloud, AWS, Google Cloud, Oracle Cloud, and more than 450 managed service providers.
Zerto for Kubernetes integrates continuous backup and disaster recovery into the application deployment lifecycle for containerized applications running on-premises or in the cloud as part of its cloud data management and protection platform. Easily protect and recover any Kubernetes application and its persistent data for accelerated delivery and deployment.
In a Kubernetes environment, Zerto for Kubernetes is installed and designed to protect next generation applications.
The installation includes the following:
| • | Zerto Kubernetes Manager (ZKM): A containerized application that manages everything required for the replication between the protected and recovery clusters, apart from the actual replication of data. ZKM interacts with ZKM-PX as its proxy to a Kubernetes cluster and VRAs in order to orchestrate replication. ZKM manages the entire environment and therefore it is required to have only one instance of it. |
| • | Zerto Kubernetes Manager Proxy (ZKM-PX): A containerized application which serves as a communication proxy between the Kubernetes cluster and the VRA. Zerto requires one ZKM-PX installed per cluster. |
| • | Virtual Replication Appliance (VRA): A containerized application which is automatically installed on each cluster node. VRAs manage the replication of data from containers to the recovery cluster. |
| • | Networking: When replicating between clusters, Zerto requires ingress to manage all cross cluster communication. If replication is done within the same cluster, there is no need for this component. |
| • | Keycloak: Keycloak is an open source identity and access management tool which is used for user and component authentication. It is deployed automatically as part of the ZKM installation, and only one instance is required. |
| • | Zerto Analytics: A Zerto user interface which provides a view over all existing VPGs. |
Zerto for Kubernetes Deployment Models
Zerto for Kubernetes can be installed on a single or multiple Kubernetes cluster environments:
Zerto for Kubernetes on a Single Kubernetes Cluster Deployment
Zerto for Kubernetes on Multiple Kubernetes Cluster Deployments
| Note: | Maintaining a separate Kubernetes cluster for Zerto for Kubernetes and Keycloak is possible, but not required. |
Review the Zerto for Kubernetes deployment models, then continue to Requirements for a Zerto Managed Kubernetes Cluster.
Zerto for Kubernetes on a Single Kubernetes Cluster Deployment
Zerto for Kubernetes on Multiple Kubernetes Cluster Deployments
In this deployment Zerto recommends installing the Zerto Kubernetes Manager on the recovery cluster.
Zerto for Kubernetes on Multiple Kubernetes Cluster Deployments - with a Separate Zerto Kubernetes Manager Cluster
In this deployment Zerto recommends installing the Zerto Kubernetes Manager on the recovery cluster.
Continue to Requirements for a Zerto Managed Kubernetes Cluster.