云服务能够
开发人员喜爱 · 开发运维团队信任

# Reference plan · review before apply
  + module.network
      private_subnet
      security_group

  + module.compute
      api_pool
      worker_pool

  ~ module.observability
      retention_policy

# Review gates
# [ ] state isolation & backend locking
# [ ] provider / resource compatibility
# [ ] quota, cost & destructive changes

# Illustrative pod-spec fragment
# Tune paths and resources per workload
containers:
  - name: api
    resources:
      requests: {cpu: "250m", memory: "256Mi"}
      limits: {memory: "512Mi"}
    startupProbe:
      httpGet: {path: /health/startup, port: 8080}
      failureThreshold: 30
      periodSeconds: 10
    readinessProbe:
      httpGet: {path: /health/ready, port: 8080}
      periodSeconds: 5
# Not a complete deployable manifest

# api / elevated-error-rate

## Triage
1. Check SLO burn rate & recent releases
2. Correlate trace_id with logs
3. Inspect downstream saturation

## Mitigation
- Route to the named incident owner
- Revert desired state when appropriate
- Validate database compatibility first

## Verify & follow up
- Confirm user-facing recovery
- Record timeline and action owners