Runbooks
This section contains operational runbooks and procedures for managing the Fawkes platform.
Overview
Runbooks provide step-by-step operational procedures for common platform tasks, incident response, and validation.
Platform Operations
Epic 1: Platform Foundation
- Epic 1 Platform Operations - Core platform operational procedures
- Epic 1 Architecture Diagrams - Platform architecture reference
Epic 3: Product Discovery
- Epic 3 Product Discovery Operations - Product discovery workflows
- Epic 3 Architecture Diagrams - Discovery architecture reference
Validation & Acceptance Testing
AT-E1-001: Azure AKS Cluster
- AT-E1-001 Validation - AKS cluster validation procedures
- Azure AKS Setup - AKS cluster setup guide
- Azure AKS Validation Checklist - Complete validation checklist
Quick Reference
Common Operations
# Check platform status
make k8s-status
# View component logs
make k8s-logs COMPONENT=backstage
# Check ArgoCD status
make argocd-status ENVIRONMENT=dev
# Validate resources
make validate-resources
# Deploy locally
make deploy-local COMPONENT=all
Troubleshooting
See the Troubleshooting Guide for common issues and solutions.
Platform engineers should keep runbooks current: an out-of-date runbook is worse than no runbook because it creates false confidence during incidents.
Related Documentation
- Operations Documentation - Day 2 operations guides
- How-To Guides - Step-by-step procedures
- Troubleshooting - Problem resolution
- Validation - Validation procedures
- Deployment - Deployment guides