Kubernetes Basics MCQ

A Pod is the smallest deployable unit in Kubernetes. It can contain one or more containers that share the same network namespace and storage volumes.

A ReplicaSet ensures that a specified number of pod replicas are running at any given time. Deployments manage ReplicaSets and provide declarative updates.

A LoadBalancer Service type provisions an external load balancer from the cloud provider (e.g., AWS ELB, GCP Load Balancer) and routes external traffic to the pods.

'kubectl logs <pod-name>' streams the logs from a container in a pod. Use -f to follow the log stream and -c to specify a container in a multi-container pod.

Namespaces provide a mechanism for isolating groups of resources within a single cluster. They are ideal for separating environments (dev, staging, prod) or teams.

Secrets are designed to store sensitive information such as passwords, tokens, and keys. Unlike ConfigMaps, Secret data is base64-encoded and can be encrypted at rest.

A DaemonSet ensures that a copy of a Pod runs on all (or some selected) nodes. Common use cases include log collectors (Fluentd), monitoring agents (Prometheus Node Exporter), and CNI plugins.

The kube-scheduler watches for newly created Pods with no assigned node and selects a node for them to run on based on resource requirements, constraints, and policies.

The default restartPolicy for a Pod is 'Always', which means Kubernetes will restart the containers in a pod whenever they exit, regardless of the exit code.

'kubectl apply -f manifest.yaml' is the declarative approach to manage Kubernetes resources. Unlike 'kubectl create', it can update existing resources without error.