Explore connectivity solutions between legacy systems and Kubernetes in this informative conference talk. Delve into the importance of stable source IPs for sender identification, firewall considerations, and the Kubernetes network model. Examine detailed network configurations, source IP handling, and community discussions within Kubernetes. Learn about Submariner's functionality and key Kubernetes concepts like headless services. Analyze on-premise configurations, cluster setups, and connection scenarios between pods and external systems through diagrams and console examples. Conclude with a summary of the problem statement regarding legacy systems' need for stable source IPs and explore related issues and pull requests.
Connectivity Between Legacy Systems and Kubernetes: Identifying Senders Using Source IPs
Overview
Syllabus
Intro
Overview of This Session
1.1. Requirement of Stable Source IPs
1.2. Firewall
2.1. Kubernetes Network Model
2.2. Details of Network Model (1/3)
2.4. Source IPs From/To k8s
2.5 Discussion in k8s Community
3.2 How Submariner Works
3.6 k8s Concepts: (2) Headless Service • Service without load balancing via Cluster P → Often used with StatefulSet to provide a unique identity for each Pod
3.8 Final Configuration On-premise
4.1 Configurations for Clusters (Diagram)
4.3 Pod to External Connection (Diagram)
4.3 Pod to External Connection (Console)
4.4 External to Pod Connection (Diagram)
4.4 External to Pod Connection (Console)
5.1. Conclusion • Problem statement: - Some legacy system require stable source is to identify senders
5.2. Related Issues and PRs
Taught by
Linux Foundation
