Term 1
ConfigMap Usage
ConfigMap Usage is the practice of storing and injecting configuration data, like environment variables or files, into containerized applications separately from the application code.
Acronym study
Terms 1–14 of 14 CKAD 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
ConfigMap Usage is the practice of storing and injecting configuration data, like environment variables or files, into containerized applications separately from the application code.
Term 2
Container logs are records of output generated by applications running inside a container, showing what the application did, errors it encountered, or status updates it produced.
Term 3
Environment variables in pods are key-value pairs that pass configuration data into containerized applications running in Kubernetes, letting the app read settings without hardcoding them.
Term 4
Events in Kubernetes are timestamped records that capture state changes, errors, and important actions happening inside a cluster, helping administrators and tools monitor and troubleshoot the system.
Term 5
Init Containers are specialized containers that run and complete before the main containers in a Kubernetes Pod start, used for setup tasks like initializing data or waiting for dependencies.
Term 6
A liveness probe is a Kubernetes health check that tells the system whether a container is running properly and should be kept alive or restarted.
Term 7
The Metrics Server is a cluster-wide aggregator of resource usage data in Kubernetes, collecting CPU and memory metrics from nodes and pods for autoscaling and monitoring.
Term 8
A Pod Security Context defines privilege and access control settings for a Pod or its containers in Kubernetes, such as which user ID to run as or which Linux capabilities to allow.
Term 9
A Kubernetes mechanism that checks if a container is ready to start accepting traffic and serve requests.
Term 10
Resource Requests and Limits are Kubernetes settings that tell the system how much CPU and memory a container needs and how much it is allowed to use at most.
Term 11
Secret Usage is the practice of storing and using sensitive information like passwords, API keys, and certificates in Kubernetes so that only authorized pods and containers can access them.
Term 12
A ServiceAccount is a Kubernetes identity used by pods to authenticate and authorize API requests to the Kubernetes cluster.
Term 13
A sidecar container is a secondary container that runs alongside a primary application container in the same Kubernetes pod, providing supporting functionality without altering the main application.
Term 14
A Kubernetes mechanism that checks whether an application inside a container has started successfully, and delays other health checks until it is ready.