node | - A machine in the cluster
- Can be physical or virtual
|  |
pod | - Group of containers running on the same host
- Configured to share a network stack and other resources such as volumes
|  |
deployments | - Requirements you give to Kubernetes regarding your applications (your Pods)
- Allows scaling, rolling updates, rollbacks
- Multiple deployments can be used together to implement a canary deployment
- Delegates pods management to replica sets
- A Kubernetes process (the scheduler) continually checks the state of all the Deployments
|  |
service | - Abstract way to expose an app as a network service
- Causes a proxy to be configured to forward requests to a set of pods
- Services are stable network endpoint to connect to one or multiple containers
- Single, unchanging IP address or DNS name which will be automatically routed to any matching Pod
- Services allow to talk to pods from within the cluster
- Service DNS names always follow this pattern:
SERVICE.NAMESPACE.svc.cluster.local
|  |
ingress | - Ingress objects are rules that define the routes to our Services
- They expose Services to the internet
|  |