DevOps Guidelines
Deployment strategy
- Rolling (default): gradual, zero-downtime replacement.
- Blue-green: duplicate environments, atomic cutover, instant rollback, 2× infrastructure.
- Canary: route a small percentage first; requires traffic splitting.
Docker
- Pin specific base-image tags (for example
node:22-alpine); NEVER use :latest.
- Use multi-stage builds and a non-root user. Copy dependencies first for caching.
.dockerignore: node_modules, .git, tests. Define HEALTHCHECK and resource limits.
Kubernetes
Configure startup, readiness, and liveness probes with workload-appropriate initial delays and thresholds.
CI/CD
- PR: lint → typecheck → unit → integration → preview.
- Main: build → staging → smoke → production.
Health and shutdown
- Simple:
GET /health → { "status": "ok" }.
- Detailed: dependencies, uptime, version.
- Services MUST expose meaningful health and gracefully handle
SIGTERM when the workload requires it.
Configuration
Use environment variables (Twelve-Factor), separated by environment. Validate at startup and fail fast. NEVER commit secrets or hard-code NODE_ENV=production.
Rollback
Kubernetes: kubectl rollout undo. Vercel: vercel rollback. Docker: redeploy the previous pinned image.
Feature Flags
- Lifecycle: create → enable → 5% → 25% → 50% → 100% → remove flag and dead code.
- Every flag MUST have an owner, expiration, and rollback trigger. Remove within two weeks.
Checklists
- Pre-deploy, when applicable: passing tests, code review, environment variables, migrations, rollback plan.
- Post-deploy services: healthy, monitored, old pods terminated, outcome documented.
- Production services: passing tests; no hardcoded secrets; JSON logs; meaningful health; pinned versions; validated environment variables; resource limits; TLS; CVE scan; CORS; rate limiting; CSP/HSTS/X-Frame-Options; tested rollback; runbook; on-call.
- Apply security/CVE checks to executable or security-sensitive workloads.
Mobile Deployment
- EAS:
eas build:configure; eas build -p ios|android --profile preview; eas update --branch production; --auto-submit.
- Fastlane: iOS
match/cert/sigh/pilot; Android Gradle/supply.
- Keep credentials in environment/secret storage, never Git. Automate iOS development/distribution signing with
fastlane match; use keytool and Google Play App Signing for Android.
- TestFlight: internal instant; external 90 days/100 testers. Google Play: internal/beta/production. Expect 1–7 days for review.
- Rollback: EAS
eas update:rollback; native release → revert build; store release → reduce phased rollout.
1---2name: gem-devops-guidelines3description: Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mobile release workflows. Use for DevOps, platform, container, pipeline, or release tasks.4---56# DevOps Guidelines78## Deployment strategy910- Rolling (default): gradual, zero-downtime replacement.11- Blue-green: duplicate environments, atomic cutover, instant rollback, 2× infrastructure.12- Canary: route a small percentage first; requires traffic splitting.1314## Docker1516- Pin specific base-image tags (for example `node:22-alpine`); NEVER use `:latest`.17- Use multi-stage builds and a non-root user. Copy dependencies first for caching.18- `.dockerignore`: `node_modules`, `.git`, tests. Define `HEALTHCHECK` and resource limits.1920## Kubernetes2122Configure startup, readiness, and liveness probes with workload-appropriate initial delays and thresholds.2324## CI/CD2526- PR: lint → typecheck → unit → integration → preview.27- Main: build → staging → smoke → production.2829## Health and shutdown3031- Simple: `GET /health` → `{ "status": "ok" }`.32- Detailed: dependencies, uptime, version.33- Services MUST expose meaningful health and gracefully handle `SIGTERM` when the workload requires it.3435## Configuration3637Use environment variables (Twelve-Factor), separated by environment. Validate at startup and fail fast. NEVER commit secrets or hard-code `NODE_ENV=production`.3839## Rollback4041Kubernetes: `kubectl rollout undo`. Vercel: `vercel rollback`. Docker: redeploy the previous pinned image.4243## Feature Flags4445- Lifecycle: create → enable → 5% → 25% → 50% → 100% → remove flag and dead code.46- Every flag MUST have an owner, expiration, and rollback trigger. Remove within two weeks.4748## Checklists4950- Pre-deploy, when applicable: passing tests, code review, environment variables, migrations, rollback plan.51- Post-deploy services: healthy, monitored, old pods terminated, outcome documented.52- Production services: passing tests; no hardcoded secrets; JSON logs; meaningful health; pinned versions; validated environment variables; resource limits; TLS; CVE scan; CORS; rate limiting; CSP/HSTS/X-Frame-Options; tested rollback; runbook; on-call.53- Apply security/CVE checks to executable or security-sensitive workloads.5455## Mobile Deployment5657- EAS: `eas build:configure`; `eas build -p ios|android --profile preview`; `eas update --branch production`; `--auto-submit`.58- Fastlane: iOS `match`/`cert`/`sigh`/`pilot`; Android Gradle/`supply`.59- Keep credentials in environment/secret storage, never Git. Automate iOS development/distribution signing with `fastlane match`; use `keytool` and Google Play App Signing for Android.60- TestFlight: internal instant; external 90 days/100 testers. Google Play: internal/beta/production. Expect 1–7 days for review.61- Rollback: EAS `eas update:rollback`; native release → revert build; store release → reduce phased rollout.
williamlimasilva