5 exercises — Practice communicating Node NotReady events, etcd degradation, cluster upgrades, and post-incident validation in professional English.
0 / 10 completed
1 / 10
Node worker-03 has been in NotReady state for 4 minutes. Pods on that node are being rescheduled. You need to post a Slack update to your engineering channel. Which message is most appropriate for a professional incident communication?
Professional incident Slack messages follow a consistent structure: severity indicator, affected component, timestamp, current impact, actions in progress, and update cadence — all in one first message.
"Not sure why. Working on it." conveys panic, not control, which erodes confidence in on-call engineers. "All services may be impacted" is an unverified claim that causes unnecessary alarm. The best message gives stakeholders what they need to make decisions: is the service down? Are we investigating or waiting? When will they hear next? Separate Slack threads can be used for technical investigation details to keep the main channel readable.
Key vocabulary:
• NotReady — node condition indicating the kubelet health check is failing; pods may be rescheduled
• rescheduled — pods evicted from the failing node and placed on healthy nodes by the scheduler
• update cadence — a committed interval for communicating incident status (every 10/15/30 minutes)
2 / 10
Your monitoring alerts that etcd commit latency has reached 800ms (alert threshold: 300ms). A manager asks why this is serious enough to escalate immediately. Which explanation is correct?
etcd is the single source of truth for all Kubernetes cluster state — every object, every status update, every secret. When etcd latency rises, the entire control plane's ability to read and write state degrades, cascading into system-wide instability.
The Kubernetes documentation formally recommends etcd commit latency below 10ms for optimal performance, with 50ms as the practical ceiling. At 800ms, the API server queue starts backing up, leader election heartbeats may miss their deadlines (triggering a re-election that briefly makes the cluster unmanageable), and controller reconciliation loops slow to a crawl. Escalation is warranted: the SRE team should check etcd disk I/O, network latency between etcd members, and disk throughput.
Key vocabulary:
• etcd — distributed key-value store that holds all Kubernetes cluster state (objects, secrets, configs)
• commit latency — time for a write operation to be acknowledged by the etcd leader and majority quorum
• leader election — Raft-based process by which etcd members agree on which node is the authoritative leader
3 / 10
You are planning a Kubernetes version upgrade from 1.28 to 1.29 and need to draft a stakeholder announcement. Which message is the most complete and professional?
A professional cluster upgrade announcement names the specific version change, the maintenance window with timezone, the procedure (control plane first, then workers), expected user impact, and any action required from other teams.
"No downtime" or "backward compatible" statements are potentially misleading — Kubernetes deprecates APIs across versions (e.g., batch/v1beta1 CronJobs were removed in 1.25). Each team must verify their manifests, Helm charts, and Kubernetes clients are compatible. "No action needed" prevents teams from doing this check. Giving 48–72 hours advance notice with a migration guide link allows teams to test against the new version before the maintenance window.
Key vocabulary:
• cordon — marks a node as unschedulable; new pods will not be placed on it
• drain — evicts all pods from a node gracefully before the node is taken offline for maintenance
• API deprecation — the removal or version change of a Kubernetes API endpoint between major versions
4 / 10
The Kubernetes API server is unreachable — all kubectl commands return "connection refused". You need to escalate immediately. Which escalation message is most appropriate?
Control plane unreachability is a SEV-1 incident — even though running pods continue via kubelet, the cluster cannot heal itself, accept deployments, or respond to configuration changes, which means any concurrent failure could be catastrophic.
"Just slow under load" normalises a critical failure. "Seems broken on my laptop" is not an appropriate first hypothesis when all kubectl commands fail. The correct escalation message is precise: it names the symptom (connection refused), the timestamp (when it started), the current impact (no new ops), the blast radius qualifier (existing workloads still running), and the immediate action (escalation). Kubernetes kubelets cache pod state locally and can run existing pods without the API server — but no liveness probe restarts, no HPA scaling, no new deployments are possible.
Key vocabulary:
• control plane — API server, scheduler, controller manager, and etcd — the "brain" of the cluster
• SEV-1 — Severity 1; highest incident tier; requires immediate response and executive notification
• kubelet — node-level agent that runs pods; can continue operating with cached state if the control plane is unreachable
5 / 10
A Kubernetes cluster upgrade has just completed. Which statement correctly describes what a thorough post-upgrade validation should confirm?
Post-upgrade validation is a multi-layer check: node health, control plane component health, certificate renewal, and end-to-end service availability — all must be confirmed before declaring the upgrade successful.
Node readiness is necessary but not sufficient. System pods in kube-system (kube-dns, kube-proxy, metrics-server) must be verified individually — a crashed CoreDNS pod passes a "nodes are Ready" check but breaks all service discovery. Certificate renewal is critical: kubeadm-managed clusters renew certificates during upgrades, but failures are silent. And an application smoke test (a real HTTP request to a user-facing endpoint) proves the full stack — nodes + networking + DNS + application — is healthy. Document every check as a runbook step.
Key vocabulary:
• smoke test — a minimal end-to-end test that verifies the core functionality is working after a change
• certificate renewal — the process of issuing new TLS certificates for cluster components; typically annual
• kube-system namespace — where Kubernetes core system components run; health indicates control plane stability
6 / 10
Alerting Context: Sarah, a Site Reliability Engineer, receives a notification from Prometheus that the average CPU utilization of Pod 'my-app' on Node 'worker-01' has spiked to 95% for the last 5 minutes. She needs to quickly inform the team about this potential performance issue.
Which Slack message is most appropriate for proactively communicating this situation?
Option 1 clearly states the issue and the affected component, providing immediate context for the team to understand the severity. Options 2 is more detailed and professional than the others, conveying urgency without alarmism. Options 3 and 4 are too vague and don't communicate the critical information – a high CPU utilization spike can quickly lead to performance degradation.
7 / 10
Code Review Comment: You're reviewing a PR that introduces a new logging mechanism for a Kubernetes deployment. The developer has included the following comment in the code:
logger.debug('Request ID: ' + request_id);
Which of the following is the MOST effective way to provide constructive feedback to the developer regarding this line?
Option 1 is simply a positive affirmation, which doesn't address the developer's coding practices. Option 2 suggests adding valuable context to the log message, improving debugging and monitoring capabilities – this is crucial for operational visibility in Kubernetes. Options 3 and 4 are distractions or suggest alternative, less appropriate solutions.
8 / 10
PR Description: You're drafting the description for a PR that updates the Kubernetes deployment configuration to use a new ingress controller. The goal is to provide sufficient information for reviewers and operators.
Which of the following statements BEST completes the PR description?
Option 2 is incomplete and doesn't explain *why* the change was made or its implications. Option 1 is completely inadequate for a PR description. Option 3 provides detailed information about the new ingress controller and highlights important configuration aspects – essential for review and operational readiness. Option 4 lacks any context or explanation.
9 / 10
Stand-up Update: During your daily stand-up, you're asked to provide an update on the progress of a Kubernetes cluster upgrade. You state: 'We upgraded the cluster.'
Which follow-up statement would be MOST helpful to add to demonstrate thoroughness and ensure operational stability?
Option 1 acknowledges completion while immediately highlighting that ongoing monitoring is critical. This demonstrates responsible operational practices. Options 2 provides a more detailed update including monitoring, which is vital after an upgrade. Options 3 and 4 are too brief and don't convey the necessary level of detail for a stand-up update.
10 / 10
Post-Upgrade Validation: After completing an upgrade to Kubernetes 1.29, your team needs to verify the stability of the cluster. Which of the following activities is MOST crucial for confirming a successful and stable upgrade?
Option 2 is technically correct but doesn't provide operational validation. Option 1 only confirms basic running status – not stability. Option 3 describes a thorough and critical validation process, including monitoring for anomalies which are essential in production environments. Restarting nodes (option 4) is rarely a sufficient post-upgrade step.
What will I practise in "Cluster Incident Communication — Kubernetes Operations | CoderLingo"?
5 advanced exercises practising Kubernetes cluster incident communication — Node NotReady, etcd latency, cluster upgrades, control plane failures, and post-upgrade validation.
How many exercises are in this module?
This module has 10 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Kubernetes Operations exercises?
Browse the full Kubernetes Operations hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.