Multi-Cloud Integration Labs

🎯 Goal: Deploy a regional GKE cluster with auto-scaling

📝 What to do:
1. Fill in the cluster name: tech-cluster
2. Select zone: us-central1-a
3. Set number of nodes: 3
4. Select machine type: e2-standard-4
5. Enable cluster autoscaling checkbox
6. Click "Create Cluster" button

💡 Tip: GKE automatically manages master nodes. You only configure worker nodes.

🎯 Goal: Set up autoscaling parameters for the node pool

📝 What to do:
1. Set minimum nodes: 1
2. Set maximum nodes: 10
3. Select disk type: pd-standard
4. Set disk size: 100 GB
5. Click "Configure Node Pool" button

🎯 Goal: Deploy a serverless container service

📝 What to do:
1. Enter service name: api-service
2. Select region: us-central1
3. Container image: gcr.io/tech-innovate/api:v1
4. Set memory: 512 MB
5. Set CPU: 1 vCPU
6. Select authentication: Allow unauthenticated
7. Click "Deploy Service" button

💡 Tip: Cloud Run automatically scales from 0 to N based on traffic.

🎯 Goal: Enable Istio-based service mesh

📝 What to do:
1. Enable Anthos Service Mesh checkbox
2. Select mesh profile: asm-managed
3. Enable traffic management
4. Enable observability features
5. Click "Enable Service Mesh" button

🎯 Goal: Create CI/CD pipeline with Cloud Build

📝 What to do:
1. Enter build trigger name: main-build
2. Select repository: github.com/tech/app
3. Branch pattern: ^main$
4. Build configuration: cloudbuild.yaml
5. Click "Create Build Trigger" button

🎯 Goal: Connect GKE to Cloud SQL database

📝 What to do:
1. Enter instance ID: tech-postgres
2. Database version: POSTGRES_14
3. Instance type: db-g1-small
4. Enable private IP checkbox
5. Enter database name: techdb
6. Click "Create Instance" button

🎯 Goal: Set up Cloud Operations monitoring

📝 What to do:
1. Enable Cloud Monitoring
2. Enable Cloud Logging
3. Set SLO target: 99.9%
4. Configure alert threshold: 95%
5. Add notification email
6. Click "Save Monitoring Config" button

🎯 Goal: Connect on-premises and AWS servers to Azure Arc

📝 What to do:
1. Select servers to onboard (check at least 2)
2. Select resource group: Arc-Hybrid-RG
3. Choose location: East US
4. Add tags: Environment=Production
5. Click "Onboard Servers" button

💡 Tip: Azure Arc extends Azure management to any infrastructure.

🎯 Goal: Register on-prem K8s cluster with Arc

📝 What to do:
1. Enter cluster name: onprem-cluster
2. Select subscription: Production-Sub
3. Resource group: Arc-Hybrid-RG
4. Location: East US
5. Click "Connect Cluster" button

🎯 Goal: Apply compliance policies across hybrid resources

📝 What to do:
1. Select policy initiative: Azure Security Benchmark
2. Choose scope: Arc-Hybrid-RG
3. Set compliance level: Audit
4. Enable remediation task checkbox
5. Click "Assign Policy" button

🎯 Goal: Set up Flux for automated K8s deployments

📝 What to do:
1. Enter configuration name: prod-gitops
2. Git repository URL: https://github.com/global/k8s-config
3. Branch: main
4. Path: /clusters/production
5. Sync interval: 5 minutes
6. Click "Enable GitOps" button

🎯 Goal: Enable unified monitoring and logging

📝 What to do:
1. Create workspace name: arc-monitor-workspace
2. Select pricing tier: Per GB
3. Enable VM Insights checkbox
4. Enable Container Insights checkbox
5. Data retention: 90 days
6. Click "Create Workspace" button

🎯 Goal: Set up monitoring alerts

📝 What to do:
1. Alert rule name: high-cpu-alert
2. Select metric: CPU Percentage
3. Threshold: 80%
4. Evaluation frequency: 5 minutes
5. Select severity: Warning (Sev 2)
6. Add action group
7. Click "Create Alert Rule" button

🎯 Goal: Verify compliance and download detailed analysis report

📝 What to do:
1. Navigate to Compliance tab (click 4th tab)
2. View overall compliance score and metrics
3. Review non-compliant resources list
4. Click "Generate Compliance Report" button
5. Click the downloaded PDF link to open and analyze your compliance report
6. Review all configurations, policies, and recommendations in the PDF

💡 Tip: The PDF contains detailed analysis of all your configurations - review it carefully!

🎯 Goal: Set up primary VPC in AWS us-east-1

📝 What to do:
1. Select cloud provider: AWS
2. VPC name: primary-vpc
3. CIDR block: 10.0.0.0/16
4. Select region: us-east-1
5. Enable DNS hostnames checkbox
6. Click "Create VPC" button

🎯 Goal: Create primary database with Multi-AZ

📝 What to do:
1. DB instance identifier: finance-primary-db
2. Engine type: PostgreSQL 14
3. Instance type: db.r5.large
4. Select Multi-AZ: Yes
5. Storage type: io1 (Provisioned IOPS)
6. IOPS: 3000
7. Click "Create Database" button

🎯 Goal: Set up secondary VPC in IBM Cloud

📝 What to do:
1. Select cloud provider: IBM Cloud
2. VPC name: dr-vpc
3. CIDR block: 10.1.0.0/16
4. Select region: us-south
5. Resource group: DR-Resources
6. Click "Create VPC" button

🎯 Goal: Create standby database in IBM Cloud

📝 What to do:
1. Service name: finance-dr-db
2. Database type: PostgreSQL 14
3. Plan: Standard
4. Memory: 8 GB
5. Disk: 20 GB
6. Click "Create Database" button

🎯 Goal: Set up cross-cloud data replication

📝 What to do:
1. Replication mode: Asynchronous
2. RPO (hours): 1 hour (use slider)
3. RTO (hours): 4 hours (use slider)
4. Sync frequency: 15 minutes
5. Enable compression checkbox
6. Click "Configure Replication" button

🎯 Goal: Configure automated failover process

📝 What to do:
1. Failover plan name: finance-dr-plan
2. Select failover mode: Test (radio button)
3. Enable health checks checkbox
4. Health check interval: 5 minutes
5. Add failover notification email
6. Click "Create Failover Plan" button

🎯 Goal: Execute and validate DR test

📝 What to do:
1. Review DR dashboard status
2. Verify replication sync is current
3. Click "Initiate Test Failover" button
4. Wait for failover completion
5. Validate DR metrics
6. Click "Generate DR Report" button