F5 Container Ingress Services (CIS) deployment using Cilium CNI and static routes
F5 Container Ingress Services (CIS) supports static route configuration to enable direct routing from F5 BIG-IP to Kubernetes/OpenShift Pods as an alternative to VXLAN tunnels.
Static rout...
Published Feb 06, 2026
Version 1.0E_Jiki
Employee
Escalation Engineer @F5Networks.
I specialize in F5 CIS deployments/troubleshooting, automating BIG-IP on AWS/Azure deployments using cloud CLI tools, infrastructure-as-code with Terraform, Go web development, and providing API-driven solutions
Tech stack: F5 CIS | Kubernetes | Terraform | Go | AWS/Azure CLI | REST APIs | Telemetry/AS3Nikoolayy1
MVP
Mar 08, 2026"static routes" is a great CIS feature as this way you don't need zebos/imish routing module on F5 to talk with bgp to the k8s cluster but why it is not available also for calico ?
- E_JikiMar 08, 2026
Employee
According to documentation, calico CNI can be selected for static route configuration. You need to specify calico-k8s in the orchestration-cni parameter. Please see https://clouddocs.f5.com/containers/latest/userguide/static-route-support.html. Cilium CNI was just for demo purposes
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)