Multi-Cluster, Multi-Cloud Networking for K8S with F5 Distributed Cloud – Deployment Guideline

Overview

This is the second part of two-part series on “Multi-Cluster, Multi-Cloud Networking for Kubernetes”. In part one, I shared some insight on why organizations deploy multiple K8S cluster and what challenges organizations encounter. I also shared on how F5 Distributed Cloud Mesh able to help to address those challenges as well as three possible Cloud Mesh architecture patterns (Cloud Mesh as pods, node and hybrid). In this article, I am going to share how you can implement and deploy those patterns in your environment.

This article leverages Cloud Mesh as Hybrid and Kubernetes use are 3 independent OpenShift Container Platform (OCP) cluster. Any OCP specific instruction can be retrofitted to fit for other Kubernetes environment (EKS, AKS, GKE). Cloud Mesh Pod is cloud and Kubernetes platform agnostic. At the time of this article, OCP, EKS, AKS and GKE are platform that validated, tested and supported.

Here the link to Part 1 – Architecture Pattern.

Before deep dive into those steps, below is a video demonstration on the outcomes and values of F5 Distributed Clouds brings. In this demo video, I also showcase how you can deploy a highly resilient application across multiple OpenShift Container Platform and apply consistent security protection on those applications. Please refer to DevCentral Github - f5xc-multicluster-mcn-for-openshift  for details of those instructions.

Demo Architecture

Demo Video - Multi-Cluster, Multi-Cloud Networking for Kubernetes - OpenShift Cluster Resiliency and Security with F5 WAAP

Related Link

Part 1 - Architecture Pattern

Devcentral Github