Kubernetes began as a way to solve problems with deploying and managing containerized applications at Google. Early versions introduced basic Kubernetes objects and the concept of pods, which are groups of containers that are deployed together. As Kubernetes was used across multiple nodes, new challenges emerged around networking, load balancing, and service discovery. Later versions introduced services, which provide a single IP and DNS name for pods, making load balancing and discovery easier. Ingresses were also added to consolidate routing rules for external access to cluster services through a single resource.

1. K8s
101
Aly Kafoury

2. History
● Problems before kubernetes
● Primitive solutions
● Kubernetes 0.1
● Introducing Kubernetes objects

3. Pods Kube 0.1
A Kubernetes pod is a group of containers that are deployed together on the
same host. If you frequently deploy single containers, you can generally replace
the word "pod" with "container" and accurately understand the concept.

4. Multi Node Problems
● Network Problems
● Abstraction
● KubeDns kube 0.4 , history of Service Discovery

5. Services
A service can be defined as a logical set of pods. It can be defined as an
abstraction on the top of the pod which provides a single IP address and DNS
name by which pods can be accessed. With Service, it is very easy to manage
load balancing configuration.

6. External Networking problems
● DNS problems
● Manual Load balancing
● Manual Service Discovery

7. Ingress
In Kubernetes, an Ingress is an object that allows access to your Kubernetes
services from outside the Kubernetes cluster. You configure access by creating
a collection of rules that define which inbound connections reach which
services. This lets you consolidate your routing rules into a single resource.