Home labs & practical projects
Restore a service after a node becomes unavailable
A project to do with your own tools, with guidance on what to create and capture.
What you could create
A small Kubernetes service loses capacity when a worker node becomes unavailable. You must explain scheduling, service endpoints and recovery.
| Evidence | What to capture |
|---|---|
| Cluster event timeline | Show the inputs, scope and decisions behind this record. The diagnosis uses cluster events rather than guessing from one failed request. |
| Recovery procedure with health checks | Include the evidence supporting your conclusion. Recovered replicas are ready and receive service traffic. |
What you'll need
Local lab
Create a disposable multi-node cluster and a small replicated application. Record initial pod placement and a request that demonstrates service health.
Project record
Keep the working files for cluster event timeline and record assumptions as you go.
Current reference material
Use the linked provider resources to verify the features, access terms and version relevant to your project.
Access & cost
Uses your own computer. Confirm hardware capacity, software licences and download terms before setup.
Use disposable VMs, containers or a simulator. Keep the lab separate from your everyday machine and work network.
Suggested milestones
- 1
Plan and investigate
Simulate a controlled node interruption and inspect pod and event state.
- 2
Develop your approach
Identify scheduling constraints that prevent recovery.
- 3
Verify and explain
Restore capacity, validate service endpoints and write the operator handover.
Useful resources
Use these resources to deepen your understanding and check key details.
Review the current provider requirements and relevant subject areas.
Check relevance, platform versions and current access terms.
Find relevant providers and check features, access requirements and costs.
A useful starting point
Create a disposable multi-node cluster and a small replicated application. Record initial pod placement and a request that demonstrates service health.
What a good result looks like
- The diagnosis uses cluster events rather than guessing from one failed request.
- Recovered replicas are ready and receive service traffic.
- The handover distinguishes temporary recovery from the underlying configuration fix.
Finish the project
Save sanitised evidence, then remove the lab instances or revert to the clean snapshot. Remove temporary accounts and credentials.
Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.