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...
Updated Mar 14, 2024
Version 12.0
MichaelOLeary
Employee
Employee
aditEmployee
EmployeeMichaelOLeary @Rebecca_Moloney
In the original Article , in Architecture 1, it stated :
Architecture 1: External Load Balancer (Secure K8s Gateway)
In a Secure Kubernetes Gateway architecture you have integration with your existing K8s platform, using the XC node as the external load balancer for your K8s cluster. In this scenario, you create a ServiceAccount and kubeconfig file to configure XC. The XC node then performs service discovery against your K8s API server. I've covered this process in a previous article, but the advantage is that you can integrate with existing K8s platforms. One disadvantage is that this is true for NodePort services only (not ClusterIP).
However when it came to the revised version in Oct 2023, this changed to :
This allows exposing both NodePort and ClusterIP services via the XC node.
Could you please let me know how we can expose via Cluster IP , because Cluster IP is internal to the cluster and provides internal connectivity , what am i missing here ?