Bootstrapping a Cluster whit Kubeadm Overview of kubeadm

1. 5 - Generates Static Pod Manifest

1.1. Generate for Control Plan Pods

1.2. File system storage

1.3. kubelet monitors

1.3.1. Find manifest

1.3.1.1. Start Statics Pods

1.3.1.1.1. /etc/kubernetes/manifests

1.3.1.1.2. etcd

1.3.1.1.3. API Server

1.3.1.1.4. Controller Manage

1.3.1.1.5. Scheduler

1.3.1.2. Monitored by the Kubelet and started automatically when the system starts and over tima

2. 6- Starts up the Control Plane

2.1. API Server Pod

2.2. ETCD Pod

3. 7 - Tainsts the Master

3.1. Never Scheduler User Pods in the Master Node

3.2. Only Scheduler System Pods

4. 8 - Generates a Bootstrap Token

4.1. Generates initialization token to join additional nodes in the cluster

5. 9 - Starts Add-On Pods: DNS and Kube-Proxy

6. Securing cluster communications

6.1. API Server use for communication

7. Initiation the cluster

8. scheduler.conf

9. 1- Kubeadm int

10. 2 - Pre-Flight checks

10.1. Appropriate resources system

10.1.1. CPU

10.1.2. Memory

10.2. Correct Permissions

10.3. Pull images fo control plan

10.3.1. Runner in the Pods

10.4. Compatible CRI

10.4.1. automatic start

11. 3 - Creates a Certificate Authority

11.1. Authentication

11.1.1. Users

11.1.2. Kubelets

11.2. Cryptographic

11.3. Self signed CA

11.3.1. Storage in /etc/kubernetes/pki

11.4. External PKI

11.4.1. Certificate Management with kubeadm

11.5. Distributes to each Node

12. 4- Generates Kubeconfig files

12.1. Authentication the Components in API Server

12.2. Used to define how to connect to your cluster

12.2.1. Certificate information

12.2.2. Cluster location

12.3. /etc/kubernetes

12.3.1. admin.conf (kubernetes-admin)

12.3.1.1. Administration account Super User in Kubernetes

12.3.2. kubelet.conf

12.3.3. Kubelet locate the API Server and present the correctly certificate client

12.3.4. controller-manager.conf