Skip to content
This repository was archived by the owner on May 13, 2024. It is now read-only.

Commit 3c23947

Browse files
authored
Updated README. Added architecture diagram (#20)
1 parent d4a4f6c commit 3c23947

File tree

2 files changed

+4
-0
lines changed

2 files changed

+4
-0
lines changed

README.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,10 @@ ErieCanal is an implementation of [Kubernetes Multi-Cluster Service API (MCS)](h
1212

1313
In the `Locality` mode, which is the default configuration, traffic is scheduled based on proximity within the local cluster or can be scheduled to a specific cluster based on topology.In the `ActiveActive` mode, the cluster provides the same traffic processing capabilities as service export (`ServiceExport`) using load balancing. In the `Failover` mode, the importing service (ServiceImport) cluster provides disaster recovery capabilities for the exporting service (ServiceExport) cluster. ErieCanal's implementation does not require the underlying Kubernetes to use a special network and does not require a unified two-layer or three-layer network between the multi-cluster networks. Therefore, it is generally applicable to Kubernetes clusters of various types of networks.
1414

15+
## Architecture
16+
17+
![ErieCanal Architecture diagram](architecture.png)
18+
1519
## Install
1620

1721
This chart bootstraps a ErieCanal deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.

architecture.png

1.21 MB
Loading

0 commit comments

Comments
 (0)