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

Poseidon-Firmament Scheduler – Flow Network Graph Based Scheduler

Poseidon-Firmament Scheduler – Flow Network Graph Based Scheduler

In this blog post, we briefly describe the novel Firmament flow network graph based scheduling approach (OSDI paper) in Kubernetes. We specifically describe the Firmament Scheduler and how it integrates with the Kubernetes cluster manager using Poseidon as the integration glue. We have seen extremely impressive scheduling throughput performance benchmarking numbers with this novel scheduling approach.

Read More
Kubernetes Operations: Prioritize Workload in Overcommitted Clusters

Kubernetes Operations: Prioritize Workload in Overcommitted Clusters

One of the benefits in adopting a system like Kubernetes is facilitating burst-able and scalable workload. Horizontal application scaling involves adding or removing instances of an application to match demand. Kubernetes Horizontal Pod Autoscaler enables automated pod scaling based on demand.

Read More