Change the way you manage applications at small data centers. Focus your clusters around their business purposes instead of where the actual hardware resides.
In the below simplified example, we have a hypothetical “operations” and “finance” set of applications. These two major sets of applications are under different management teams, have different end-users, and have different security policies. In a traditional MDC systems using Kubernetes clusters, an individual local k8s cluster would be deployed at each MDC.
In reality multiple k8s clusters might be deplyed at each location. The Kubernetres flavor could be an “edge” oriented k8s variatin such as k3s or microk8s. In order to manage all these clusters the staff had best employee some sort of “multicloud” software set, sometimes termed Multicloud Networking Software or MCNS. This means using a propritary, non-k8s API to manage all your clusters.
The amount of clusters in this design is what drives the complexity. And many clusters are needed in order to manage applications at each site.
Izuma Cloud allows clusters to have nodes which run in multiple physical networks and at many locations. Using this capability the design can be simplifed:
Here we have taken what was at least 6 clusters plus a multicloud services API and turned it into just 2 clusters: one for operations and one for finance.
Since Izuma Cloud instances are still true k8s clusters, this solution can still be used with a multicloud solution if desired. Each Izuma Cloud instance can be managed entirely separately if needed or managed by the same team.
And a new micro data center location can be setup very quickly. No new cluster needs to be built. Machines simply need to have Izuma Edge installed and attached to the existing cluster.