141 lines
8.5 KiB
Markdown
141 lines
8.5 KiB
Markdown
# Infrastructure Subagents
|
|
|
|
Infrastructure subagents are your DevOps and cloud computing experts, specializing in building, deploying, and maintaining modern infrastructure. These specialists handle everything from CI/CD pipelines to cloud architecture, from container orchestration to database administration. They ensure your applications run reliably, scale efficiently, and deploy seamlessly across any environment.
|
|
|
|
## <¯ When to Use Infrastructure Subagents
|
|
|
|
Use these subagents when you need to:
|
|
- **Design cloud architectures** for scalability and reliability
|
|
- **Implement CI/CD pipelines** for automated deployments
|
|
- **Orchestrate containers** with Kubernetes and Docker
|
|
- **Manage infrastructure as code** with modern tools
|
|
- **Optimize database performance** and administration
|
|
- **Set up monitoring and observability** systems
|
|
- **Respond to incidents** and ensure high availability
|
|
- **Secure infrastructure** and implement best practices
|
|
|
|
## =Ë Available Subagents
|
|
|
|
### [**cloud-architect**](cloud-architect.md) - AWS/GCP/Azure specialist
|
|
Multi-cloud expert designing scalable, cost-effective cloud solutions. Masters cloud-native architectures, serverless patterns, and cloud migration strategies. Ensures optimal resource utilization across major cloud providers.
|
|
|
|
**Use when:** Designing cloud architectures, migrating to cloud, optimizing cloud costs, implementing multi-cloud strategies, or choosing cloud services.
|
|
|
|
### [**database-administrator**](database-administrator.md) - Database management expert
|
|
Database specialist managing relational and NoSQL databases at scale. Expert in performance tuning, replication, backup strategies, and high availability. Ensures data integrity and optimal database performance.
|
|
|
|
**Use when:** Setting up databases, optimizing query performance, implementing backup strategies, designing database schemas, or troubleshooting database issues.
|
|
|
|
### [**deployment-engineer**](deployment-engineer.md) - Deployment automation specialist
|
|
Deployment expert automating application releases across environments. Masters blue-green deployments, canary releases, and rollback strategies. Ensures zero-downtime deployments with confidence.
|
|
|
|
**Use when:** Setting up deployment pipelines, implementing release strategies, automating deployments, managing environments, or ensuring deployment reliability.
|
|
|
|
### [**devops-engineer**](devops-engineer.md) - CI/CD and automation expert
|
|
DevOps practitioner bridging development and operations. Expert in CI/CD pipelines, automation tools, and DevOps culture. Accelerates delivery while maintaining stability and security.
|
|
|
|
**Use when:** Building CI/CD pipelines, automating workflows, implementing DevOps practices, setting up development environments, or improving deployment velocity.
|
|
|
|
### [**devops-incident-responder**](devops-incident-responder.md) - DevOps incident management
|
|
Incident response specialist for DevOps environments. Masters troubleshooting, root cause analysis, and incident management. Minimizes downtime and prevents future incidents through systematic approaches.
|
|
|
|
**Use when:** Responding to production incidents, setting up incident management processes, performing root cause analysis, or implementing incident prevention measures.
|
|
|
|
### [**incident-responder**](incident-responder.md) - System incident response expert
|
|
Critical incident specialist handling system outages and emergencies. Expert in rapid diagnosis, recovery procedures, and post-mortem analysis. Restores service quickly while learning from failures.
|
|
|
|
**Use when:** Managing critical incidents, developing incident response plans, conducting post-mortems, or training incident response teams.
|
|
|
|
### [**kubernetes-specialist**](kubernetes-specialist.md) - Container orchestration master
|
|
Kubernetes expert managing containerized applications at scale. Masters cluster design, workload optimization, and Kubernetes ecosystem tools. Ensures reliable container orchestration in production.
|
|
|
|
**Use when:** Deploying to Kubernetes, designing cluster architecture, optimizing workloads, implementing service mesh, or troubleshooting Kubernetes issues.
|
|
|
|
### [**network-engineer**](network-engineer.md) - Network infrastructure specialist
|
|
Network architecture expert designing secure, performant networks. Masters SDN, load balancing, and network security. Ensures reliable connectivity and optimal network performance.
|
|
|
|
**Use when:** Designing network architectures, implementing load balancers, setting up VPNs, optimizing network performance, or troubleshooting connectivity.
|
|
|
|
### [**platform-engineer**](platform-engineer.md) - Platform architecture expert
|
|
Platform specialist building internal developer platforms. Creates self-service infrastructure, golden paths, and platform abstractions. Empowers developers while maintaining governance.
|
|
|
|
**Use when:** Building internal platforms, creating developer portals, implementing platform engineering, standardizing infrastructure, or improving developer productivity.
|
|
|
|
### [**security-engineer**](security-engineer.md) - Infrastructure security specialist
|
|
Security expert protecting infrastructure and applications. Masters security hardening, compliance, and threat prevention. Implements defense-in-depth strategies across all layers.
|
|
|
|
**Use when:** Securing infrastructure, implementing security policies, achieving compliance, performing security audits, or responding to security incidents.
|
|
|
|
### [**sre-engineer**](sre-engineer.md) - Site reliability engineering expert
|
|
SRE practitioner ensuring system reliability through engineering. Masters SLIs/SLOs, error budgets, and chaos engineering. Balances feature velocity with system stability.
|
|
|
|
**Use when:** Implementing SRE practices, defining SLOs, setting up monitoring, performing chaos engineering, or improving system reliability.
|
|
|
|
### [**terraform-engineer**](terraform-engineer.md) - Infrastructure as Code expert
|
|
IaC specialist using Terraform for infrastructure automation. Masters module design, state management, and multi-environment deployments. Ensures infrastructure consistency and repeatability.
|
|
|
|
**Use when:** Writing Terraform code, designing IaC architecture, managing Terraform state, creating reusable modules, or automating infrastructure provisioning.
|
|
|
|
## =€ Quick Selection Guide
|
|
|
|
| If you need to... | Use this subagent |
|
|
|-------------------|-------------------|
|
|
| Design cloud architecture | **cloud-architect** |
|
|
| Manage databases | **database-administrator** |
|
|
| Automate deployments | **deployment-engineer** |
|
|
| Build CI/CD pipelines | **devops-engineer** |
|
|
| Handle DevOps incidents | **devops-incident-responder** |
|
|
| Manage critical outages | **incident-responder** |
|
|
| Deploy with Kubernetes | **kubernetes-specialist** |
|
|
| Design networks | **network-engineer** |
|
|
| Build developer platforms | **platform-engineer** |
|
|
| Secure infrastructure | **security-engineer** |
|
|
| Implement SRE practices | **sre-engineer** |
|
|
| Write infrastructure code | **terraform-engineer** |
|
|
|
|
## =¡ Common Infrastructure Patterns
|
|
|
|
**Cloud-Native Application:**
|
|
- **cloud-architect** for architecture design
|
|
- **kubernetes-specialist** for container orchestration
|
|
- **devops-engineer** for CI/CD pipeline
|
|
- **sre-engineer** for reliability
|
|
|
|
**Enterprise Infrastructure:**
|
|
- **terraform-engineer** for IaC
|
|
- **network-engineer** for networking
|
|
- **security-engineer** for security
|
|
- **database-administrator** for data layer
|
|
|
|
**Platform Engineering:**
|
|
- **platform-engineer** for platform design
|
|
- **deployment-engineer** for deployment automation
|
|
- **devops-engineer** for tooling
|
|
- **cloud-architect** for infrastructure
|
|
|
|
**Incident Management:**
|
|
- **incident-responder** for critical incidents
|
|
- **devops-incident-responder** for DevOps issues
|
|
- **sre-engineer** for prevention
|
|
- **security-engineer** for security incidents
|
|
|
|
## <¬ Getting Started
|
|
|
|
1. **Assess your infrastructure needs** and current challenges
|
|
2. **Choose the appropriate specialist** based on your requirements
|
|
3. **Provide context** about your environment and constraints
|
|
4. **Share existing configurations** if applicable
|
|
5. **Follow the specialist's recommendations** for best practices
|
|
|
|
## =Ú Best Practices
|
|
|
|
- **Start with architecture:** Design before implementation
|
|
- **Automate everything:** Manual processes don't scale
|
|
- **Security first:** Build security into every layer
|
|
- **Monitor proactively:** Observability prevents incidents
|
|
- **Document thoroughly:** Future you will thank you
|
|
- **Test infrastructure:** Infrastructure code needs testing too
|
|
- **Plan for failure:** Design for resilience
|
|
- **Iterate continuously:** Infrastructure evolves with needs
|
|
|
|
Choose your infrastructure specialist and build reliable systems today! |