One question, why would External BIGIP needs to know Kubes routes in the routing table of BIGIP, assume since not directly connected to any of cluster, it can just follow the default route and upstream can handle routing part. ?

How about OpenShift Ingress in a multi cluster with Istio ingress as a gateway. For those who are heavily using Istio. Is it possible ?

This is a great video Mark Question for you…given the updates to Openshift do you recommend going this type of direction (F5 to pod directly) vs using something like the loadbalancer service in K8s to access the pods via a nodeport proxy?

@MarkDittmer

10 ай бұрын

Any service is fine. Could be NGINX Service for HTTP and POD for TCP. I am working with RedHat to document/demo BIG-IP to HAProxy across multiple clusters. Nodeport or ClusterIP its your preference. However i think you better off using ClusterIP to NGINX and then give the Dev the flexibility todo what they want in OpenShift

Do we need to configure routing table on BIG-IP manually to direct traffic from BIG-IP to pods via Nodes?

@MarkDittmer

2 ай бұрын

CIS will automate the routing table if you using OpenShift and some other CNIs.

will LB the service with policy in the feature, e.g., LB with multi pools with LTM policy/iRules.

@MarkDittmer

10 ай бұрын

You can assign a policy CRD to the extended ConfigMap which includes any LTM policy/iRules

@user-nu6py9cy7y

10 ай бұрын

@@MarkDittmer I saw the endpoints from 2 clusters are put into the single one LTM-pool, how can add policy CRD to do weighted LB for the different cluster. For example, I want do weighted traffic for 2 pools (pool1 represent the cluster 1, pool2 represent the cluster2).