🎭 Scenario 01: Chaos Strikes Manual Deployments

"Python K8s Automation Saves the Day!"

📖 SCENARIO OVERVIEW

The Challenge

Chaos Agent has infiltrated your Kubernetes deployments! Manual kubectl commands are failing left and right due to missing namespaces, broken ConfigMaps, and service misconfigurations. Your team is frustrated, deployments are unreliable, and production is at risk.

The Hero Solution

Deploy a bulletproof Python automation system that handles Kubernetes deployments with enterprise-grade reliability. No more manual errors, no more missing dependencies, no more chaos!

What You'll Build

🐍 Python Kubernetes Client automation
🗳️ Interactive Vote Application for real-world testing
📊 Real-time Monitoring System for deployment health
🛡️ Chaos-proof Deployment Process with error handling

⏱️ TIME ALLOCATION

Activity	Duration	Type
Live Demo (Instructor)	10 minutes	👀 Watch
Your Deployment	5 minutes	🛠️ Hands-on
App Interaction	5 minutes	🎮 Interactive
Total	20 minutes

🎯 LEARNING OBJECTIVES

By completing this scenario, you will:

✅ Understand why manual Kubernetes deployments fail
✅ Master Python Kubernetes client library basics
✅ Implement automated resource creation and management
✅ Experience enterprise-grade error handling
✅ Build monitoring and observability systems
✅ Defeat Chaos Agent's manual deployment attacks! 🦸‍♂️

🧨 THE CHAOS AGENT'S ATTACK

"Your manual kubectl commands are unreliable! Watch me break your deployments with 'simple' configuration errors! Good luck debugging YAML hell in production!" 😈

What Chaos Agent Breaks: - ❌ Missing namespaces cause deployment failures - ❌ Wrong ConfigMap names break application startup
- ❌ Service misconfigurations prevent access - ❌ Missing resource limits cause production chaos - ❌ No health checks = unknown application state

🦸‍♂️ THE PYTHON HERO'S RESPONSE

"Not so fast, Chaos Agent! Python automation makes deployments bulletproof. Watch this!"

How Python Hero Wins: - ✅ Automatic namespace management - creates if missing - ✅ Dependency handling - ConfigMaps before deployments
- ✅ Configuration validation - catches errors before applying - ✅ Best practices enforcement - resource limits, health checks - ✅ Graceful error handling - conflicts and failures managed - ✅ Real-time monitoring - know exactly what's happening

📁 FILE STRUCTURE

scenarios/01-python-deploy/
├── README.md                          # This comprehensive guide
├── demo-script.sh                     # Instructor live demo script
├── chaos/
│   ├── broken-vote-app.yaml          # Intentionally broken for demo
│   └── chaos-explanation.md          # What's wrong with manual approach
├── hero-solution/
│   ├── deploy-vote-app.py            # 🚀 Main Python deployment automation
│   ├── monitor-deployment.py         # 📊 Real-time monitoring system
│   ├── requirements.txt              # Python dependencies
│   └── k8s-manifests/               # Generated Kubernetes resources
│       ├── namespace.yaml
│       ├── configmap.yaml
│       ├── deployment.yaml
│       └── service.yaml
├── participant-guide.md               # Step-by-step participant instructions
└── troubleshooting.md                # Complete troubleshooting guide

🚀 QUICK START (For Participants)

Prerequisites

✅ Kubernetes cluster running (Docker Desktop, Minikube, or EKS)
✅ Python 3.8+ installed
✅ kubectl configured and working

Step 1: Environment Setup (2 minutes)

# Navigate to this scenario
cd scenarios/01-python-deploy

# Install Python dependencies
pip3 install -r hero-solution/requirements.txt

# Verify your cluster connection
kubectl cluster-info

Step 2: Deploy with Python Automation (3 minutes)

# Run the Python hero solution
python3 hero-solution/deploy-vote-app.py

Expected Output:

🚀 Initializing Python K8s Hero System...
✅ Hero system ready to defeat Chaos Agent!
📁 Creating namespace: vote-app
✅ Namespace created successfully
⚙️  Creating ConfigMap with poll configuration
✅ ConfigMap created with poll settings
🚀 Creating bulletproof deployment
✅ Deployment created with health checks and resource limits
🌐 Creating service for external access
✅ Service created - accessible at port 30001
⏳ Waiting for deployment to be ready...
🎉 Deployment ready! 2/2 pods running
🎯 ACCESS YOUR VOTE APP:
   💻 Local: http://localhost:30001
   🌐 Minikube: http://$(minikube ip):30001
   ☁️  EKS: http://<any-node-ip>:30001
🎉 CHAOS AGENT DEFEATED!

Step 3: Access Your Vote Application (5 minutes)

The script will provide environment-specific access instructions based on auto-detection:

🐳 Docker Desktop Environment:

💻 Primary: http://localhost:31000
🔄 If blocked: Use port forwarding below

🎯 Minikube Environment:

🌐 Minikube: http://<minikube-ip>:31000 (auto-detected)
🚀 Auto-open: minikube service vote-app-service -n vote-app
💡 Manual IP: minikube ip

☁️ Cloud Environment (EKS/GKE/AKS):

🌍 Get node IP: kubectl get nodes -o wide
🔗 Access: http://<any-external-ip>:31000

🌐 Universal Access (Always Works):

# This works on ANY Kubernetes environment - no conflicts!
kubectl port-forward svc/vote-app-service -n vote-app 31500:80

# Then access: http://localhost:31500
# Note: Uses port 31500 to avoid Jenkins (8080) and MkDocs (8000) conflicts

Step 4: Interact with Your Vote App (5 minutes)

Once you access the vote app through any of the above methods:

🗳️ Cast Your Vote:
Select your favorite programming language
Click "Vote" button
See your vote recorded instantly
📊 Watch Real-time Results:
View the live chart updating
See vote percentages change
Notice the interactive features
🔄 Test Multiple Votes:
Try different browsers
Vote multiple times (each counts!)
Refresh page and see persistence
🎮 Challenge Others:
Share your URL with neighbors
See collaborative voting
Watch real-time updates from multiple users

Step 5: Monitor Your Deployment (5 minutes)

# Run the monitoring system
python3 hero-solution/monitor-deployment.py

# Choose option:
# 1 = One-time status check
# 2 = Continuous monitoring (Press Ctrl+C to stop)

🎬 LIVE DEMO WALKTHROUGH (For Instructors)

Demo Script Overview

Part 1: Chaos Agent Strikes (3 minutes)

# Show the chaos - run this live
./demo-script.sh

What Students See: 1. Manual deployment fails - missing namespace 2. Fix namespace, still fails - missing ConfigMap
3. Create ConfigMap manually, still fails - service misconfiguration 4. Frustration mounts - "This is production reality!"

Part 2: Python Hero Saves the Day (4 minutes)

# Run the hero solution
python3 hero-solution/deploy-vote-app.py

Key Teaching Points: - ✨ Automation handles all dependencies - ✨ Error handling prevents failures - ✨ Best practices applied automatically - ✨ Monitoring built-in from the start

Part 3: Victory Celebration (3 minutes)

Show the working vote app
Demonstrate real-time voting
Highlight the automation benefits
Celebrate defeating Chaos Agent!

🧪 CHAOS TESTING

Test 1: Kill Pods and Watch Recovery

# Kill a random pod
kubectl get pods -n vote-app -o name | xargs -I {} kubectl delete {} --grace-period=0

# Watch Kubernetes recreate it automatically
kubectl get pods -n vote-app -w

Test 2: Scale Up/Down

# Scale up to 5 replicas
kubectl scale deployment vote-app -n vote-app --replicas=5

# Scale down to 1 replica
kubectl scale deployment vote-app -n vote-app --replicas=1

Test 3: Resource Pressure

# Create resource pressure
kubectl run stress-test --image=busybox --requests=cpu=1000m,memory=1Gi --limits=cpu=2000m,memory=2Gi --command -- stress --cpu 4 --vm 2 --vm-bytes 1G

📊 MONITORING & OBSERVABILITY

Real-time Monitoring

# Watch pod status
kubectl get pods -n vote-app -w

# Monitor service endpoints
kubectl get endpoints -n vote-app

# Check resource usage
kubectl top pods -n vote-app

Logs and Debugging

# View application logs
kubectl logs -f deployment/vote-app -n vote-app

# Check events
kubectl get events -n vote-app --sort-by='.lastTimestamp'

🎯 SUCCESS CRITERIA

✅ Scenario 01 Complete Checklist:

✅ Python automation deployed successfully
✅ Vote application accessible and functional
✅ Real-time voting working
✅ Monitoring system operational
✅ Chaos Agent defeated! 🦸‍♂️

Key Learning Outcomes:

✅ Python Kubernetes Client - Mastered automation
✅ Error Handling - Graceful failure management
✅ Best Practices - Resource limits and health checks
✅ Monitoring - Real-time observability
✅ Chaos Resilience - Survived pod failures

🚀 NEXT STEPS

What's Next:

Scenario 02: Enterprise Security with Secret Management
Scenario 03: Auto-scaling with HPA
Scenario 04: Blue-Green Deployment Strategies
Scenario 05: GitOps with ArgoCD and Argo Rollouts

Production Readiness:

Apply these Python automation patterns to your real applications
Implement comprehensive error handling
Add monitoring and alerting
Test chaos scenarios regularly

🆘 TROUBLESHOOTING

Common Issues:

Issue: Python dependencies not found

# Solution: Install requirements
pip3 install -r hero-solution/requirements.txt

Issue: Kubernetes connection failed

# Solution: Check cluster status
kubectl cluster-info
kubectl get nodes

Issue: Port already in use

# Solution: Use different port
kubectl port-forward svc/vote-app-service -n vote-app 31501:80

Issue: Pods not starting

# Solution: Check events and logs
kubectl get events -n vote-app
kubectl describe pod -n vote-app

🎉 CONCLUSION

Congratulations! You've successfully defeated Chaos Agent's manual deployment attacks! 🦸‍♂️

What You've Accomplished:

✅ Automated Kubernetes deployments with Python
✅ Built a real interactive application (vote app)
✅ Implemented enterprise-grade error handling
✅ Created comprehensive monitoring systems
✅ Proven chaos resilience through testing

Key Takeaways:

Automation is essential for reliable deployments
Error handling prevents production failures
Monitoring provides real-time visibility
Testing chaos scenarios builds confidence

You're now ready for the next challenge: Enterprise Security! 🔐

Remember: In the world of Kubernetes, automation is your superpower against chaos! 🚀