Connectivity Between Legacy Systems and Kubernetes: Identifying Senders Using Source IPs

Connectivity Between Legacy Systems and Kubernetes: Identifying Senders Using Source IPs

Linux Foundation via YouTube Direct link

Intro

1 of 18

1 of 18

Intro

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Connectivity Between Legacy Systems and Kubernetes: Identifying Senders Using Source IPs

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 Overview of This Session
  3. 3 1.1. Requirement of Stable Source IPs
  4. 4 1.2. Firewall
  5. 5 2.1. Kubernetes Network Model
  6. 6 2.2. Details of Network Model (1/3)
  7. 7 2.4. Source IPs From/To k8s
  8. 8 2.5 Discussion in k8s Community
  9. 9 3.2 How Submariner Works
  10. 10 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
  11. 11 3.8 Final Configuration On-premise
  12. 12 4.1 Configurations for Clusters (Diagram)
  13. 13 4.3 Pod to External Connection (Diagram)
  14. 14 4.3 Pod to External Connection (Console)
  15. 15 4.4 External to Pod Connection (Diagram)
  16. 16 4.4 External to Pod Connection (Console)
  17. 17 5.1. Conclusion • Problem statement: - Some legacy system require stable source is to identify senders
  18. 18 5.2. Related Issues and PRs

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.