Taints and Tolerations are a scheduling pair: a taint repels Pods from a node unless the Pod carries a matching toleration, giving fine control over placement. CKA Domain 4 uses them with node affinity to place or isolate workloads.
A Pod is the smallest deployable unit in Kubernetes, wrapping one or more containers that share network and storage.
kubectl is the command-line client used to inspect and control a Kubernetes cluster through the API server.
kubeadm is the official tool for bootstrapping a Kubernetes cluster and performing control-plane version upgrades.
etcd is the distributed key-value store that holds all Kubernetes cluster state.
The control plane is the set of components — API server, scheduler, controller manager, and etcd — that manage the cluster's desired state.
The kubelet is the node agent that starts and monitors the Pods assigned to its node.
A Deployment manages a replicated, self-healing set of Pods and supports rolling updates and rollbacks.
A Service gives a stable virtual IP and DNS name to a changing set of Pods, with types ClusterIP, NodePort, and LoadBalancer.
An Ingress routes external HTTP and HTTPS traffic to Services based on host and path rules, and requires a running Ingress controller.
A NetworkPolicy specifies which connections are allowed to and from Pods, defaulting to deny once a Pod is selected.
CoreDNS is the default in-cluster DNS server that resolves Service and Pod names to addresses.
A PersistentVolumeClaim (PVC) is a Pod's request for storage that binds to a PersistentVolume, often provisioned dynamically through a StorageClass.
A StorageClass defines a class of storage and enables dynamic provisioning of PersistentVolumes on demand.
Taints and Tolerations are a scheduling pair: a taint repels Pods from a node unless the Pod carries a matching toleration, giving fine control over placement.
Role-Based Access Control (RBAC) grants permissions through Roles and ClusterRoles bound to users or ServiceAccounts.