Kubernetes service with ha
•Download as PPTX, PDF•
2 likes•428 views
This document discusses methods for providing high availability services in Kubernetes including NodePort, cloud provider load balancers, Ingress, and Keepalived VIP. NodePort exposes services on each node's IP at a static port. Cloud provider load balancers rely on the cloud platform to provide an external IP for services. Ingress is for HTTP load balancing but does not fully support external networking. Keepalived VIP uses a virtual IP address, IP to service mapping, and daemonset to provide high availability services on bare metal clusters without a cloud provider.
Report
Share
Kubernetes service with ha
- 1. Kubernetes Service with High Availability 1
- 2. Me 鄭偉聖, Sam Zheng CS student in NCTU Intern in National Center for High-performance Computing (NCHC) Intern in Industrial Technology Research Institute (ITRI) Familiar with OpenStack, Docker and Kubernetes kweisamx.cs05g@g2.nctu.edu.tw 2
- 4. 4
- 5. 5
- 6. How do we to export the service IP to public network on bare metel? In kubernetes we have some existed solution NodePort CloudProvider Load Balancer Ingress But it is enough? 6
- 7. NodePort 7 kubeProxy kubeProxy kubeProxy NodePort NodePort NodePort Pod Pod Pod
- 8. NodePort 8 kubeProxy kubeProxy kubeProxy NodePort NodePort NodePort Pod Pod Pod
- 9. Load Balancer Cloud Provider e.g. AWS , GCP, OpenStack Load Balancer is created by Cloud Provider, and provide the external IP to for service But it is only for Cloud Provider, the bare metal cannot do this 9
- 10. Load Balancer 10 kubeProxy kubeProxy kubeProxy NodePort NodePort NodePort Cloud LoadBalancer Pod Pod Pod
- 11. 11
- 12. Ingress 12 HTTP Load Balancing SSL Termination Content-base Rourting Not fully for external network
- 15. Ingress 15 kubeProxy kubeProxy kubeProxy Pod PodPodPod PodPod Momo.foo.com Jojo.foo.com yoyo.foo.com hostnetwork
- 16. Ingress 16 kubeProxy kubeProxy kubeProxy Pod PodPodPod PodPod DNS
- 17. 17
- 18. Keep-Alived VIP Real High-Availability Virtual IP Address IP to Service Configmap DaemonSet 18 Ref : - https://github.com/kubernetes/contrib/tree/master/keepalived-vip
- 19. Keep-Alived VIP 19 kubeProxy kubeProxy kubeProxy Pod PodPod Keepalived Keepalived Keepalived 140.113.1.1 140.113.1.2 140.113.1.3 Vip: 140.113.1.50
- 20. Keep-Alived VIP 20 kubeProxy kubeProxy kubeProxy PodPodPod Keepalived Keepalived Keepalived 140.113.1.1 140.113.1.2 140.113.1.3 Vip: 140.113.1.50 Pod
- 21. Keep-Alived VIP 21 kubeProxy kubeProxy kubeProxy PodPodPod Keepalived Keepalived Keepalived 140.113.1.1 140.113.1.2 140.113.1.3 Vip: 140.113.1.50
- 22. 22
- 23. Keep-Alived VIP + Ingress 23 kubeProxy kubeProxy kubeProxy PodPod Pod Keepalived Keepalived Keepalived 140.113.1.1 140.113.1.2 140.113.1.3 Vip: 140.113.1.50 Momo.foo.com ojo.foo.com
- 24. Summary Just have fun or Test – NodePort Using Cloud to build your kubernetes – Cloud Load Balancer Using DNS to provide your service – Ingress VIP – keepalived-VIP 24