Kubernetes network deep dive: Did you make the right choice?

Kubernetes network deep dive: Did you make the right choice?

  • February 23, 2019
Table of Contents

Kubernetes network deep dive: Did you make the right choice?

Kubernetes networking design can be intimidating, especially when you are the one to make decisions for cluster-level network choices. In this session, we will discuss how these choices will affect cluster routing and load balancing, focusing on KubeProxy modes(iptables vs IPVS) and network solutions. The main purpose of this blog is to help Kubernetes users to get comfortable with K8S major network components, common usage patterns, and corresponding troubleshooting tools.

This will provide a good foundation for you to design your next cluster or to analyze your existing cluster network issues and make suggestions for improvements. First question, KubeProxy is a critical and required component in all K8S clusters, which mode is the right one for you? iptable or IPVS? Next, how to choose the best L2/L3 network solution?

KubeRouter, Calico, Flannel or others? After deploying the cluster and have the network up and running. What tools can I use to verify expected behavior for routing and load balancing?

Source: itnext.io

Share :
comments powered by Disqus

Related Posts

Kubernetes Metrics and Monitoring

Kubernetes Metrics and Monitoring

This post explores the current state of metrics and monitoring in Kubernetes by walking through the gradual thought process that I experienced when learning this topic. Kubernetes needs some metrics for it’s basic out-of-the-box functionality, like autoscaling and scheduling. This is regardless of any monitoring solution you may want for the purpose of troubleshooting and alerting.

Read More