An analytics team needs nightly reports that retry on failure and never starve other apps of resources.
The detailed steps, checklists and trainer review open in the SOTT student portal for enrolled students.
E-commerce: Black Friday without a crash. A shop ran on fixed VMs and fell over every time traffic tripled. The services moved to Kubernetes with Horizontal Pod Autoscalers and cluster autoscaling. The site handled three times normal traffic and scaled back down overnight.
Banking: Many teams, one shared cluster. Forty teams each ran their own servers, with different patching and security levels. A shared Kubernetes platform with namespaces, RBAC, quotas and network policies per team. Teams deploy on their own while security rules apply to everyone.
SaaS: Self-healing services. Engineers were paged at night to restart crashed processes by hand. Deployments with probes restart unhealthy pods and reschedule them away from failed nodes. Night-time pages for crashes dropped sharply.
Yes. Once your trainer approves it, list it under Projects with the tools you used, one line on the problem it solves and a link to your repository and demo video.
About 10 hours of hands-on work, and it fits best after week 8 of the CKAD (Certified Kubernetes Application Developer) course.
Enrolled students get every task with steps, "done when" checks, the submission form and a trainer review in the SOTT student portal.