In this webinar, you’ll learn how Kubernetes makes applications available outside of a Kubernetes cluster. We’ll approach this from a networking perspective of understanding how Kubernetes has its own Container Network Interface (CNI) that is used to facilitate communication between pods (containers). Next, we’ll look at the Kubernetes Service type to understand how the choice of “ClusterIP,” “NodePort,” “HostPort,” and “LoadBalancer” can affect the availability of a service and its performance. We’ll also look at the “Ingress” resource type and how it’s used to provide L7 (content-routing) of HTTP and HTTPS traffic.
After looking at the internals of how Kubernetes operate, we’ll learn how BIG-IP interacts with a Kubernetes cluster using NodePort or via a CNI like Flannel or Calico (VXLAN/BGP). This interaction is facilitated by the use of F5 Container Ingress Services to automate the configuration of the BIG-IP instance.
Lastly, we’ll look at how NGINX Ingress Controller differs from the Kubernetes project NGINX Ingress Controller (yes, same name, different authors) in supporting the Kubernetes Ingress resource type for L7 routing of HTTP and HTTPS traffic.
Throughout the webinar we’ll demo pertinent aspects of Kubernetes, F5 BIG-IP, and NGINX related to networking and support of Kubernetes resources.
Kubernetes networking resource types (Service/Ingress)
BIG-IP to connect to a Kubernetes cluster network
NGINX Ingress Controller support of Kubernetes Ingress resources