mirror of
https://github.com/azaion/gps-denied-onboard.git
synced 2026-06-22 22:41:13 +00:00
Oleksandr Bezdieniezhnykh
1f634c2604
ci/woodpecker/push/02-build-push Pipeline failed
- Modified the autodev state to reflect the current testing phase and details of the new `jetson-e2e` tests. - Enhanced the "How to Test" documentation to provide clearer instructions on the demo replay validation process, including video and tlog alignment steps. - Updated architectural documentation to include the new demo replay operator flow and its dependencies. - Documented the removal of deprecated auto-sync features and clarified the operator-facing UI for replay validation. - Added new entries in the dependencies table for upcoming tasks related to the demo replay flow. These changes improve clarity and usability for operators and developers working with the demo replay system.
2.0 KiB
2.0 KiB
Step 6: Deployment Procedures
Role: DevOps / Platform engineer Goal: Define deployment strategy, rollback procedures, health checks, and deployment checklist. Constraints: Procedures document — no implementation.
Steps
-
Define deployment strategy:
- Preferred pattern: blue-green / rolling / canary (choose based on architecture)
- Zero-downtime requirement for production
- Graceful shutdown: 30-second grace period for in-flight requests
- Database migration ordering: migrate before deploy, backward-compatible only
-
Define health checks:
| Check | Type | Endpoint | Interval | Threshold |
|---|---|---|---|---|
| Liveness | HTTP GET | /health/live |
10s | 3 failures → restart |
| Readiness | HTTP GET | /health/ready |
5s | 3 failures → remove from LB |
| Startup | HTTP GET | /health/ready |
5s | 30 attempts max |
-
Define rollback procedures:
- Trigger criteria: health check failures, error rate spike, critical alert
- Rollback steps: redeploy previous image tag, verify health, rollback database if needed
- Communication: notify stakeholders during rollback
- Post-mortem: required after every production rollback
-
Define deployment checklist:
- All tests pass in CI
- Security scan clean (zero critical/high CVEs)
- Database migrations reviewed and tested
- Environment variables configured
- Health check endpoints responding
- Monitoring alerts configured
- Rollback plan documented and tested
- Stakeholders notified
Self-verification
- Deployment strategy chosen and justified
- Zero-downtime approach specified
- Health checks defined (liveness, readiness, startup)
- Rollback trigger criteria and steps documented
- Deployment checklist complete
Save action
Write deployment_procedures.md using templates/deployment_procedures.md.
Blocking
BLOCKING: Present deployment procedures to user. Do NOT proceed until confirmed.