d4c3e452fb
* Created WhatTheHack template stub * Update Challenge-00.md Initial creation * Update Challenge-00.md Initial Creation * Update Challenge-01.md Initial Creation of Challenge * Update Challenge-00.md Update link to next challenge * Update Challenge-02.md Initial creation of challenge * Update Challenge-03.md Initial creation of challenge * Update Challenge-03.md Update challenge number * Create Challenge-04.md * Update README.md Initial creation of readme * Create ContosoPizzaApp Creation of App folder * Delete ContosoPizzaApp * Create ContosoPizzaApp * Add files via upload Initial App Upload * Delete ContosoPizzaApp delete dummy file * Update README.md Updated links * Update README.md added ability to bring your own application * Update Challenge-00.md Added use your own AKS application for this hack * Update Challenge-01.md Updated Success Criteria * Update Challenge-00.md Added K8s language * Update Challenge-04.md Added DevOps and Pizza Application language * Delete Lectures.pptx * Add files via upload Uploaded Lecture * Update Challenge-01.md Updated Title * Update Challenge-02.md Updated title * Update Challenge-02.md Updated title * Update Challenge-03.md * Update Challenge-04.md Updated title and application language * Update README.md Added sections * Update README.md change type of access to contributor * Update README.md Intermediate understanding of AKS / K8s * Add files via upload added zip file * Update README.md updated prerequisites * Update README.md added to optional requirements * Update Solution-00.md * Update Solution-00.md creation of guide * Update Solution-00.md Added NSG for Vnet * Update Solution-01.md initial creation of challenge * Update Challenge-01.md removed a tip for scaling the PODs * Update Solution-01.md Added command box * Update Solution-01.md * Update Solution-01.md Updated JSON spec * Update Solution-01.md * Update Solution-01.md * Update Solution-01.md Added kubectl commands * Update Solution-01.md Updated kubectl commands * Update Solution-01.md updated bullets * Update Challenge-01.md Updated bullets * Update Solution-02.md draft challenge 2 * Update Challenge-02.md removed tips and moved to coach guide * Update Solution-01.md changed deployment to statefulset * Update Challenge-01.md update tips for statefulset * Update Solution-02.md Updated workflow bullets * Update Solution-02.md Updated workflow bullets * Update Challenge-03.md Updated Tips * Update Solution-03.md Added traffic manager profile info * Update Solution-03.md Added Geo Peeker info * Update Challenge-02.md update success criteria * Update Challenge-03.md Updated success criteria * Update README.md Updated Agenda * Update README.md Added Day 2 * Create Solution-04.md * Update Solution-04.md * Update README.md * Update Solution-03.md added navigation setting * Update README.md removed repo contains section * Delete resources.zip * Create EastUS-AKS * Delete EastUS-AKS * Create test * Delete test * Add files via upload * Add files via upload * Delete xxx-ChaosStudio4AKS/Student/Resources/EastUS-AKS directory * Delete xxx-ChaosStudio4AKS/Student/Resources/WestUS-AKS directory * Added AKS files for East-US deployment * West-US deployment files * Delete xxx-ChaosStudio4AKS/ContosoPizzaApp directory * Update README.md updated Title of hack * Update README.md Removed XXX * Update README.md * Update README.md * Update README.md * Create 55 -ChaosStudio4AKS * Add files via upload * Delete Lectures.pptx?raw=true * Update Solution-02.md * Lecture * Lecture * upadted punc * format * name change on hack * updated AKS version * delete zip file * Lectures.pptx raw * removed raw pptx * added raw pptx * removed non raw pptx * fixing raw issue * removed old raw file * Delete xxx-ChaosStudio4AKS directory removed old XXX-ChaosStudio4AKS * Delete 55 -ChaosStudio4AKS * Making typo updates to the hack * Update README.md added questionmark * Update Challenge-00.md added 00 * Update Solution-04.md added [Optional] Injecting Chaos into your CI/CD pipeline * Update README.md Prerequisites - Ready, Set, GO! to challenge 00 to match * Update Challenge-02.md change to AZ in title versus Availability Zone * Update README.md updated title for [Optional] Injecting Chaos into your CI/CD pipeline * Update README.md added [ * Update Solution-00.md change - to : * Update Solution-01.md change - to : * Update Solution-02.md change - to : * Update Solution-03.md change - to : * Update Solution-04.md change - to : * Update Challenge-01.md change - to : * Update Challenge-02.md change - to : * Update Challenge-03.md change - to : * Update Challenge-04.md change - to : * Update README.md Updates Day 2 to show 4 hour duration * Update Challenge-03.md added "Verify application is available after WestUS region is offline" * Update Challenge-01.md - If your application went offline, what change could you make to the application? - Rerun the experiment and verify if the change was successful * Adding solution to challenge 4 and updating some verbiage * Create .wordlist.txt * Update .wordlist.txt * Update Solution-00.md * Update Solution-01.md * Update .wordlist.txt * Update .wordlist.txt * Update Solution-02.md * Update .wordlist.txt * Update Solution-03.md * Update Solution-03.md * Update .wordlist.txt * Update Solution-00.md * Update README.md * Update Challenge-00.md * Update Challenge-01.md * Update Challenge-03.md * Update Challenge-04.md * Update Challenge-00.md * Update .wordlist.txt * Update Challenge-01.md * Update README.md * Update README.md * Update README.md * Update .wordlist.txt * Update Solution-04.md * Update README.md * Update Solution-00.md added "can be done" * Update Solution-01.md * Update Solution-01.md * Update Solution-01.md fixed typos * Update Solution-01.md * Update Challenge-00.md Fixed some typos * Update Challenge-01.md Fixed typos * Update Challenge-01.md fixed typo * Update Challenge-01.md * Update Challenge-02.md Fixed typos * Update Challenge-03.md fixed typos * Update Challenge-04.md fixed typos --------- Co-authored-by: GitHub Actions Bot <> Co-authored-by: Andy Huang <54148527+Whowong@users.noreply.github.com> Co-authored-by: Pete Rodriguez <perktime@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| Coach | ||
| Student | ||
| .wordlist.txt | ||
| README.md | ||
README.md
What The Hack - ChaosStudio4AKS
Introduction
Azure Chaos Studio (Preview) is a managed service for improving resilience by injecting faults into your Azure applications. Running controlled fault injection experiments against your applications, a practice known as chaos engineering, helps you to measure, understand, and improve resilience against real-world incidents, such as a region outages or application failures causing high CPU utilization on a VMs, Scale Sets, and Azure Kubernetes.
Learning Objectives
This “What the Hack” WTH is designed to introduce you to Azure Chaos Studio (Preview) and guide you through a series of hands-on challenges to accomplish the following:
- Leverage the Azure Chaos Studio to inject failure into an application/workload
- Provide hands-on understanding of Chaos Engineering
- Understand how resiliency can be achieved with Azure
In this WTH, you are the system owner of the Contoso Pizzeria Application (or you may bring your own application). Super Bowl Sunday is Contoso Pizza's busiest time of the year, the pizzeria ordering application must be available during the Super Bowl.
You have been tasked to test the resiliency of the pizzeria application (or your application). The pizzeria application is running on Azure and you will use Chaos Studio to simulate various failures.
Challenges
- Challenge 00: Prerequisites - Ready, Set, GO!
- Deploy the multi-region Kubernetes pizzeria application
- Challenge 01: Is your application ready for the Super Bowl?
- How does your application handle failure during large scale events?
- Challenge 02: My AZ burned down, now what?
- Can your application survive an Azure outage of 1 or more Availability Zones?
- Challenge 03: Godzilla takes out an Azure region!
- Can your application survive a region failure?
- Challenge 04: Injecting Chaos into your CI/CD pipeline
- Optional challenge, using Chaos Studio experiments in your CI/CD pipeline
Prerequisites
- Azure subscription with contributor access
- Visual Studio Code terminal or Azure Shell (recommended)
- Latest Azure CLI (if not using Azure Shell)
- GitHub or Azure DevOps to automate Chaos Testing
- Azure fundamentals, Vnets, NSGs, Scale Sets, Traffic Manager
- Fundamentals of Chaos Engineering
- Intermediate understanding of Kubernetes (kubectl commands)and AKS
Learning Resources
- What is Azure Chaos Studio
- What is Chaos Engineering
- How Netflix pioneered Chaos Engineering
- Embrace the Chaos
- Why you should break more things on purpose --AWS, Azure, and LinkedIn case studies
Contributors
- Jerry Rhoads
- Kevin Gates
- Andy Huang
- Tommy Falgout