The document provides an overview of Kubernetes architecture, detailing key components like etcd, API server, controller manager, scheduler, Docker containers, kubelet, and proxy. It explains the functions of each component, including how they interact within the cluster to manage workloads and configuration. Additionally, it offers a hands-on approach to deploying a single-node Kubernetes cluster using Minikube, emphasizing operational commands with kubectl.

2. MIHIR SHAH | SHAHENSHAH
Twitter: shahenshah9999
www.github.com/shahenshah99
medium.com/@shahenshah

3. WHY KUBERNETES?

4. Kubernetes Vs. Docker Swarm

5. UNDERSTANDING THE KUBERNETES
ARCHITECTURE

7. Components in the architecture
1. Etcd
2. API Server
3. Controller manager
4. Scheduler
5. Docker containers
6. Kubelet Service
7. Proxy Service

8. Etcd
It stores the configuration information which can
be used by each of the nodes in the cluster.

9. API Server
Kubernetes is an API server which provides all the
operation on cluster using the API
Kubeconfig is a package along with the server side tools
that can be used for communication. It exposes
Kubernetes API.

10. Controller Manager
This component is responsible for most of the collectors that regulates the
state of cluster and performs a task.
The key controllers are replication controller, endpoint controller,
namespace controller, and service account controller. The controller
manager runs different kind of controllers to handle nodes, endpoints, etc.

11. Schedulers
It is a service in master responsible for distributing the
workload. It is responsible for tracking utilization of working
load on cluster nodes and then placing the workload on
which resources are available and accept the workload.

12. Docker Containers
The first requirement of each node is Docker which helps
in running the encapsulated application containers in a
relatively isolated but lightweight operating environment.

13. Kubelets
This is a small service in each node responsible for
relaying information to and from control plane service. It
interacts with etcd store to read configuration details and
write values.
It manages network rules, port forwarding, etc.

14. Proxy
It helps in forwarding the request to correct containers and
is capable of performing primitive load balancing. It makes
sure that the networking environment is predictable and
accessible and at the same time it is isolated as well. It
manages pods on node, volumes, secrets, creating new
containers’ health checkup, etc.

15. Master-Node Structure

17. ENOUGH OF IT ALREADY, LETS GET HANDS-ON

18. Deploying a single node cluster using Minikube

19. Let’s kick in some colors
Enabling Web Dashboard

20. Starting containers using kubectl
kubectl run <deployment> http --image=<image_name> --
replicas=1
Kubectl get deployments
Kubectl describe deployment <deployment>

21. Exposing Ports
kubectl expose deployment <deployment_name> --
external-ip="172.17.0.32" --port=8000 --target-port=80
Try Curl-ing at the IP

22. Monitor the Services
Kubectl get svc
Docker ps | grep ‘<image>’