External Service Load Balancing in Kubernetes with Calico BGP

9th chunk of `content/en/blog/_posts/2016-10-00-Kubernetes-And-Openstack-At-Yahoo-Japan.md`

78e985b72454374d30679dfeb40ac604ebebc3ccd45747500000000100000484

](https://s.yimg.jp/images/tecblog/2016-1H/os_n_k8s/network.png)

In Project Calico, broadcast production IP by BGP working on BIRD containers (OSS routing software) launched on each nodes of Kubernetes. By default, it broadcast in cluster only. By setting peering routers outside of clusters, it makes it possible to access a Pod from outside of the clusters. **External Service Load Balancing**

There are multiple choices of external service load balancers (access to services from outside of clusters) for Kubernetes such as NodePort, LoadBalancer and Ingress. We could not find solution which exactly matches our requirements. However, we found a solution that almost matches our requirements by broadcasting Cluster IP used for Internal Service Load Balancing (access to services from inside of clusters) with Project Calico BGP which enable External Load Balancing at Layer 4 from outside of clusters.



 ![](https://lh3.googleusercontent.com/CsOiOnIOI_EVNmlsasU47LTyY53GZp1br2Ww83dFf8i5IMvO0o84rOhZEIAt9zTskYvsDKO0rjAwa9WZtkeAw8IE6NmzUEktDTAn8TDvQneD5yg_TQWBmg-qwvWyuU9CYLKzUUkA)

Title: External Service Load Balancing in Kubernetes with Calico BGP

Summary

The document discusses external service load balancing in Kubernetes, mentioning options like NodePort, LoadBalancer, and Ingress. However, the chosen solution involves broadcasting the Cluster IP, which is typically used for internal service load balancing, with Project Calico BGP. This enables Layer 4 external load balancing, allowing access to services from outside the Kubernetes cluster.