Kubernetes architecture options with F5 Distributed Cloud Services

  Summary F5 Distributed Cloud Services (F5 XC) can both integrate with your existing Kubernetes (K8s) clusters and/or host a K8s workload itself. Within these distinctions, we have multiple arch...
k8s-arch-options.png
Updated Mar 14, 2024
Version 12.0
cloud
F5 Distributed Cloud
kubernetes
Multicloud Networking
Securing K8 AI Applications
series-architecture-patterns
series-deployment-patterns
Foo-Bang_Chan's avatar
Foo-Bang_Chan
Icon for Employee rankEmployee
Jan 11, 2024

Hi Nikoolayy1 

Generally, modern CNI does provides access to the CluserIP. What need to happend is to route those respective subnet to the K8S nodes and the CNI will handel the routing to the internal pods. OpenShift used to require you to create VXLAN tunnel to the cluster IP due to it using OpenShiftSDN. With OCP 4.9 (if I am not wrong), Redhat default cni to OVN-Kubernetes, which support direct to the cluster ip. EKS, AKS (Azure CNI), GKE and Calico a few of those that I know support direct to the cluster IP. AKS (Kubenet) don't. So, its CNI dependent. F5 CIS relied on the CNI to send traffic. You can run Cluster mode or tunnel mode.