Updating a Shop Within Its Quota is a practical project for learners who have completed Kubernetes basics. Publish a fresh shop catalogue when ordinary operation fits the namespace's CPU request quota but the attempted rolling update does not. Keep the protected reference shop working and hand over the real updated catalogue.
One Guided Lab teaches the resource calculation, update strategy, recovery and customer checks. One independent Challenge changes the allocation and availability requirement for a bookshop, so you must choose a strategy that fits the new conditions. Each unit starts with its own prepared environment.
What You Will Learn
After completing this course, you will be able to:
- distinguish a ReplicaSet's failed Pod creation due to quota from an existing Pod that cannot be scheduled;
- calculate steady and temporary CPU requests, including a protected neighbouring workload;
- choose a RollingUpdate budget that respects both a fixed quota and a minimum number of available replicas;
- preserve the original workloads and Services, keep the approved baseline, and recover an unsuccessful update attempt;
- connect the saved release manifest to the real new catalogue and a complete CSV download;
- interpret recorded cluster and service samples without presenting them as a production uptime guarantee.
Who This Course Is For
This course is for Kubernetes beginners ready to apply their foundation to a complete delivery task.
Prerequisites: Basic terminal paths and Tab navigation, simple YAML, and familiarity with Pods, Deployments, Services and labels. CPU request units, ResourceQuota and the rollout calculation are explained in the guided work.
Learning environment: A prepared real single-node Kubernetes cluster, shop application and catalogue data are provided. Use the browser's Workspace, Shop and Reference Tabs to configure the update, browse its results and keep the separate reference service working. The runtime website, labels and command output are in English.
Frequently Asked Questions
Do I need prior Kubernetes experience?
Yes. You should recognise the basic objects and read a simple manifest. This project teaches the quota/update decision rather than introducing Kubernetes from scratch.
Do I need to install a cluster or write application code?
No. The cluster, application and health checks are prepared. You edit the supplied rollout strategy, use the real services and save the catalogue download.
How does the Challenge extend the Guided Lab?
The bookshop has different CPU requests, spare allocation and a stricter availability floor. Apply the same calculation and recovery methods independently; copying the guided parameter values does not satisfy its requirements.
Does this prove uninterrupted availability or performance?
No. The project checks a complete update using recorded samples in its single-node training environment. CPU requests are resource accounting, not measured utilisation, a performance promise or a monetary budget. The observations do not prove uptime between samples.
