Term 1
ClusterIP NodePort LoadBalancer
ClusterIP, NodePort, and LoadBalancer are three types of Kubernetes Services that control how traffic reaches your application pods inside the cluster or from outside.
Acronym study
Terms 1–30 of 33 CKA acronyms and key terms. Each entry includes a plain-English definition and a link to the full 800-word glossary page with exam context and practice questions.
Term 1
ClusterIP, NodePort, and LoadBalancer are three types of Kubernetes Services that control how traffic reaches your application pods inside the cluster or from outside.
Term 2
CNI plugins are modular software components that configure container network interfaces according to the Container Network Interface specification, allowing containers to communicate within a Kubernetes cluster.
Term 3
A ConfigMap is a Kubernetes object that lets you store configuration data separately from your application code, so you can change settings without rebuilding or redeploying your container images.
Term 4
A container runtime is software that runs containers by using the host operating system's kernel to isolate processes, manage filesystem layers, and handle networking.
Term 5
CoreDNS is a fast, flexible, and pluggable Domain Name System (DNS) server that is often used as the cluster DNS for Kubernetes, translating service names into IP addresses so containers can find each other.
Term 6
A DaemonSet is a Kubernetes object that ensures a copy of a specific pod runs on every node in a cluster, or on a subset of nodes.
Term 7
A Kubernetes resource that manages a set of identical Pods, ensuring they run the correct number of replicas and can be updated or rolled back without downtime.
Term 8
Etcd backup and restore is the process of saving and recovering the key-value store that holds all Kubernetes cluster data, ensuring the cluster can be rebuilt after a disaster or corruption.
Term 9
An Ingress Controller is a specialized component that manages external access to services in a Kubernetes cluster by processing Ingress resources and routing traffic according to defined rules.
Term 10
Ingress Resources are Kubernetes API objects that manage external access to services inside a cluster, typically HTTP and HTTPS traffic, by defining rules for routing requests based on hostnames and paths.
Term 11
A Kubernetes Job is a controller that runs one or more Pods to completion for a finite task, while a CronJob schedules Jobs to run at specific times or intervals.
Term 12
kubeadm is a command-line tool that helps you create and manage a Kubernetes cluster by automating the setup of control plane and worker nodes.
Term 13
kubectl is the command-line tool used to interact with and manage Kubernetes clusters by sending commands to the Kubernetes API.
Term 14
kubectl debug is a Kubernetes command that creates a temporary container in a pod to help troubleshoot and diagnose issues without affecting the running application.
Term 15
Kubernetes architecture is the structural design of a system that automatically deploys, scales, and manages containerized applications across a cluster of machines.
Term 16
Kubernetes Node Roles are labels assigned to machines in a cluster that define whether a node runs application containers (worker) or manages the cluster (control plane).
Term 17
A Kubernetes Service is a stable network endpoint that connects a set of pods to internal or external traffic, providing consistent access even as pods change.
Term 18
Log analysis is the process of reviewing and interpreting system-generated records to understand what happened in an application or infrastructure.
Term 19
A Kubernetes resource that controls how pods communicate with each other and with other network endpoints, acting as a firewall for pod-to-pod traffic.
Term 20
Network troubleshooting is the systematic process of identifying, diagnosing, and resolving problems in a computer network to restore normal operation.
Term 21
Node Affinity is a set of rules used by Kubernetes to determine which nodes a pod can be scheduled on, based on labels assigned to the nodes.
Term 22
Node failure troubleshooting is the process of identifying, diagnosing, and resolving issues when a worker node in a Kubernetes cluster becomes unavailable or unhealthy.
Term 23
A Persistent Volume Claim (PVC) is a request for storage resources in Kubernetes, allowing a pod to consume abstracted storage without knowing the underlying storage details.
Term 24
A Persistent Volume is a piece of storage in a Kubernetes cluster that has been provisioned by an administrator and exists independently of any single pod that uses it.
Term 25
Pod Design refers to the patterns, strategies, and best practices for defining and structuring Kubernetes Pods to run containerized applications reliably and efficiently.
Term 26
Pod failure troubleshooting is the process of identifying and resolving issues that cause Kubernetes pods to crash, restart, or become unavailable.
Term 27
Resource Quotas are Kubernetes policies that limit the total amount of compute resources (like CPU and memory) that can be consumed by all containers running in a particular namespace.
Term 28
Secrets Management is the practice of securely storing, accessing, and rotating sensitive information like passwords, API keys, and certificates in a controlled and automated way.
Term 29
A Kubernetes resource that manages stateful applications by providing stable network identities and persistent storage for each pod.
Term 30
A Storage Class in Kubernetes is a template that defines how persistent storage is provisioned automatically, including the type of storage, performance characteristics, and provisioning policies.