Kubestronaut

Core concepts Cluster Architecture Master node: orchestrate nodes → schedule, monitor, worker, state, manage cluster Worker node: host applications as container Master node components: ETCD: database of the state of the cluster KUBE-SCHEDULER: schedule pods to worker nodes CONTROLLER-MANAGER NODE-CONTROLLER: orchestrate nodes REPLICATION-CONTROLLER: orchestrate replication groups KUBE-APISERVER: expose k8s cluster from external thought api Worker node components: CONTAINER RUNTIME: container runtime engine KUBELET: agent that run in every node, for receive api call from api server KUBE-PROXY: manage communication between container, nodes Container runtime interface Container runtime interface CRI: allow to use k8s with all container runtime ...

Introduction Passing the Kubernetes and Cloud Native Associate (KCNA) exam was a great milestone in my cloud journey. In this post, I’ll walk you through the strategy I used to prepare and pass the exam on the first attempt. I focused on hands-on experience, curated courses, and repeated quiz practice to reinforce core concepts. Why KCNA? KCNA is a foundational certification offered by the Cloud Native Computing Foundation (CNCF). It’s designed to validate your understanding of Kubernetes, cloud-native principles, container orchestration, and open-source tools in the CNCF landscape. ...

KCNA Kubernetes architecture Simple definitions Node: node is a worker machine where container run Cluster: set of node Master node: orchestrate the nodes Components Api server: frontend of the architecture. With api server you can talk with the cluster etcd: Distributed Hash Table **(**DHT) that contains all info of the cluster kubelet: agent that run in all node. Run stop container, interact with the kube api server of the master. container runtime: runtime where containers run controller: control the state of the cluster, restart pods if fails scheduler: distribute works on the nodes Kubectl CLI command for talk with the cluster ...