Kubernetes Services networking

Services are one of the key Kubernetes primitives you need to understand to glue microservices together and expose your applications outside of the cluster. The Service resource provides an abstract way to expose an application running on a set of Pods as a network service. Sounds simple, but what’s the difference between a Cluster IP, Node Port, and Load Balancer service? And how do all these abstractions translate to real under the covers networking behavior?

This short video explains all this and more!

In the video you’ll learn:

* How pods consume services within the cluster (Cluster IPs).

* The different ways a service can be consumed outside of the cluster (Node Ports, Load Balancers, and Service IP advertisement).

* What is External Traffic Policy and how does it impact a service?

* How Services and Network Policy interact.

* How all this works under the covers in concrete networking terms.

* What differences Calico’s native service handling capabilities bring to the picture compared to kube-proxy.

Happy watching!

🔗Project Calico Resources You Might Need

[danielvega]

I am a full stack developer and at the beginning I couldn't grasp any of all this devops thing, I couldn't understand deeply in detail what docker, k8s, jenkins, iac and all that stuff was until I realised these aren't technologies about developing but networking, so I started to study networking fundamentals and suddenly all makes sense. Devops is all about networking! I wish somebody would have told me that before, I mean, I am a programmer, I am all the day thinking about patterns, features and bugs, nothing to do with devops.

[AliHussein-goqx]

Nice Explanation. Iink it would be preferred if you replace the hand with only a pen.

[KrishnaKumar-udcj]

Very well explained underlying details this is the way I am looking for it 👍