F5 Container Ingress Service

Installation

Installation über Helm Chart mit Beispiel values.yaml

https://clouddocs.f5.com/containers/latest/userguide/cis-installation.html

Manual Installation

https://clouddocs.f5.com/containers/latest/userguide/kubernetes/

Deployment Options

Via NodePort oder ClusterIP

https://clouddocs.f5.com/containers/latest/userguide/config-options.html

NodePort

Similar to Docker, BIG-IP communicates with an ephemeral port, but in this case the kube-proxy keeps track of the backend Pod (container). This works well, but the downside is that you have an additional layer of load balancing with the kube-proxy.

ClusterIP

The BIG-IP CIS also supports a cluster mode where Ingress traffic bypasses the Kube-proxy and routes traffic directly to the pod. This requires that the BIG-IP have the ability to route to the pod. This could be by using an overlay network that F5 supports (Flannel VXLAN, or OpenShift VXLAN). Leave the kube-proxy intact (no changes to underlying Kubernetes infrastructure).