The backend server decapsulates it and responds directly to the client IP with the public IP as source (169.61.23.130 in my example). The NLB (MUX) encapsulates the packet into an IPIP tunnel packet and sends the original packet over to a backend server. The client usually connects to the first in the list. By registering multiple A (or AAAA) records for the same host name, the DNS resolver will return all of them-usually as a permuted list for each query. Feel free to skip these sections if you are familiar with DNS RR, ALB, NLB, and DSR concepts.ĭNS round robin is one of the simplest ways to distribute traffic between servers that have different individual IP addresses. In this article, we will go through a few deployment patterns and include examples so that you can pick the one that is closest to your requirements and refine further.īefore we jump into the deployment patterns, let’s quickly go through a few different load balancing types since I will be referring to these concepts later. There are multiple ways to deploy IBM Cloud Kubernetes Service clusters and the applications within, depending on your applications’ requirements. This article discusses the capabilities of this LoadBalancer service and a few deployment patterns around it, providing examples along the way.Īt IBM, it is very important to us that you can maximize your investment dollars in your IBM Cloud Kubernetes Service clusters with both efficiency and availability. With the upcoming release of Kubernetes version 1.12 on IBM Cloud Kubernetes Service, we are releasing the new IKS LoadBalancer 2.0 for public beta so that customers may test. Exploring the new IBM Cloud Kubernetes Service LoadBalancer 2.0
0 kommentar(er)
