Skip to content

Multi-network Configuration

Multi-network Configuration is a specific deployment topology within the context of Istio Multicluster Architectures, categorized alongside the Primary-Remote configuration^[400-devops-07-monitoring-and-observability-k8s-istio-samples-multicluster-readme.md]. It addresses the challenge of enabling communication and load balancing for clusters that reside on different networks^[400-devops-07-monitoring-and-observability-k8s-istio-samples-multicluster-readme.md].

Implementation

To facilitate traffic flow between disparate networks, the configuration utilizes a dedicated infrastructure component designed to separate internal mesh traffic from external Ingress traffic^[400-devops-07-monitoring-and-observability-k8s-istio-samples-multicluster-readme.md]. This requires the deployment of an East-West Gateway on the primary cluster^[400-devops-07-monitoring-and-observability-k8s-istio-samples-multicluster-readme.md].

The actual enabling of cross-cluster load balancing is achieved by applying specific Kubernetes manifests that expose services through this gateway^[400-devops-07-monitoring-and-observability-k8s-istio-samples-multicluster-readme.md]. This is typically executed via a command such as kubectl apply -f samples/multicluster/expose-services.yaml -n istio-system^[400-devops-07-monitoring-and-observability-k8s-istio-samples-multicluster-readme.md].

Sources

  • 400-devops-07-monitoring-and-observability-k8s-istio-samples-multicluster-readme.md