Forum Discussion
Amr_Ali
MVP
MVPCentral Manager service IP and pod IP
Dears,
I can not understand what the need to configure two different networks for services and pod on F5 central Manager as shown below screenshot
- Nikoolayy1
As F5 NEXT Central Manager (CM) is basically a kubernetes control node (k3s that is optimized Kubernetes) for such questions you can also check the kubernetes docs. In kubernetes it is normal to have different ip address ranges for pods and services . In many cases some security rules can blocks pod ranges but allow pods to reach other pods through services "In Kubernetes, Services are an abstract way to expose an application running on a set of Pods. Services can have a cluster-scoped virtual IP address (using a Service of type: ClusterIP). Clients can connect using that virtual IP address, and Kubernetes then load-balances traffic to that Service across the different backing Pods." Also the pod and service network should not overlap.
Service ClusterIP allocation | Kubernetes
- Nikoolayy1
Any more questions about this Amr_Ali ?
