Kubernetes Architecture & Container Orchestration Mastery Flashcards

Question 1

Deployment

Accepted Answer

A higher-level object that declaratively manages `ReplicaSets` and `Pods`. Supports automated rolling updates, rollbacks, and scaling.

Question 2

ClusterIP Service

Accepted Answer

The default Kubernetes `Service` type. Exposes the service on a cluster-internal IP, making it reachable only from within the cluster.

Question 3

NodePort Service

Accepted Answer

Exposes a `Service` on each Node's IP at a static port (in the range `30000-32767`). Automatically routes traffic to an underlying `ClusterIP` service.

Question 4

Kubernetes Control Plane Components

Accepted Answer

The master component governing cluster state, consisting of:
- `kube-apiserver`: Exposes the K8s API.
- `etcd`: Key-value store for all cluster data.
- `kube-scheduler`: Assigns unscheduled Pods to Nodes.
- `kube-controller-manager`: Runs controller processes (e.g., Node Controller, ReplicaSet Controller).

Question 5

etcd

Accepted Answer

A consistent, highly available key-value store used as Kubernetes' backing store for all cluster state and configuration data.

Question 6

Worker Node Components

Accepted Answer

Services running on every worker node to maintain running pods:
- `kubelet`: Agent ensuring containers are running in a Pod.
- `kube-proxy`: Maintains network rules and performs connection forwarding.
- `Container Runtime`: Software responsible for running containers (e.g., `containerd`, `CRI-O`).

Question 7

Pod

Accepted Answer

The smallest deployable computing unit in Kubernetes. A Pod wraps one or more containers that share storage, network IP, and execution options.

Question 8

ReplicaSet

Accepted Answer

A controller that ensures a specified number of identical Pod replicas are running at any given time, maintaining application availability.

Question 9

LoadBalancer Service

Accepted Answer

Exposes a `Service` externally using a cloud provider's external load balancer. Automatically creates `NodePort` and `ClusterIP` routings.

Question 10

Ingress

Accepted Answer

An API object that manages external HTTP/HTTPS access to services within a cluster, providing features like URL routing, SSL/TLS termination, and name-based virtual hosting.

Question 11

ConfigMap

Accepted Answer

An API object used to store non-confidential data in key-value pairs. Used to decouple environment-specific configuration from container image definitions.

Question 12

Secret

Accepted Answer

An API object used to store sensitive data like passwords, OAuth tokens, and SSH keys. By default, stored base64-encoded in `etcd`.

Question 13

PersistentVolume (PV) vs PersistentVolumeClaim (PVC)

Accepted Answer

- `PersistentVolume (PV)`: A storage resource in the cluster provisioned by an admin or dynamically.
- `PersistentVolumeClaim (PVC)`: A request for storage by a user/Pod that consumes `PV` resources based on size and access modes.

Question 14

Liveness Probe vs Readiness Probe

Accepted Answer

- `Liveness Probe`: Determines if a container needs to be restarted due to failure or deadlock.
- `Readiness Probe`: Determines if a container is ready to accept incoming network traffic.

Question 15

Namespace

Accepted Answer

A logical abstraction for isolating cluster resources between multiple users, teams, or environments (e.g., `dev`, `staging`, `prod`).

Question 16

Command: Declarative Management with `kubectl apply`

Accepted Answer

Applies a configuration change to a resource from a file or stdin:
```bash
kubectl apply -f manifest.yaml
```

Question 17

Command: Inspecting Resources with `kubectl get` and `kubectl describe`

Accepted Answer

- List resources: ```bash kubectl get pods -n ``` - Inspect detailed resource state and events: ```bash kubectl describe pod ```

Question 18

Command: Viewing Container Logs with `kubectl logs`

Accepted Answer

Fetches logs from a specific container inside a Pod: ```bash kubectl logs -f -c ``` *(`-f` streams logs in real-time)*

Question 19

Command: Executing Commands in a Pod with `kubectl exec`

Accepted Answer

Opens an interactive terminal session inside a running container:
```bash
kubectl exec -it <pod-name> -- /bin/bash
```

Question 20

Command: Managing Deployment Rollouts with `kubectl rollout`

Accepted Answer

- Check deployment status: ```bash kubectl rollout status deployment/ ``` - Undo a deployment (rollback): ```bash kubectl rollout undo deployment/ ```

Kubernetes Architecture & Container Orchestration Mastery

Cards in this deck

Related Flashcard Sets

TypeScript - Modern JavaScript Development & Type Safety

Monash FIT9132 - Data Mining & Machine Learning Fundamentals

Biochemistry - Metabolic Pathways & Regulation

JLPT N2 - Advanced Japanese Grammar, Vocabulary & Kanji