The following is the schedule for gamedays in FY26 and FY27. We’re assigning these in a round-robin style, so the schedule continues until every team has had an opportunity to do each Gameday. The teams are free to schedule the gameday at their convenience, but they must be completed by the end of the quarter.
We currently have 4 different types of gameday.
- Gitaly
- Patroni/pgbouncer
- HAProxy/Traffic Routing
- CI Runners
The following teams have been identified as necessary to perform gamedays and be familiar with our Disaster Recovery processes.
Gameday | Team |
---|
HAproxy | Foundations |
pgbouncer/patroni | Durability |
Gitaly | Observability |
CI Runners | DB Operations |
Gameday | Team |
---|
HAproxy | Runway |
pgbouncer/patroni | Delivery: Release |
Gitaly | Delivery: Deployments |
CI Runners | Foundations |
Gameday | Team |
---|
HAproxy | Durability |
pgbouncer/patroni | Observability |
Gitaly | DB Operations |
CI Runners | Runway |
Gameday | Team |
---|
HAproxy | Delivery: Release |
pgbouncer/patroni | Delivery: Deployments |
Gitaly | Foundations |
CI Runners | Durability |
Gameday | Team |
---|
HAproxy | Observability |
pgbouncer/patroni | DB Operations |
Gitaly | Runway |
CI Runners | Delivery: Release |
Gameday | Team |
---|
HAproxy | Delivery: Deployments |
pgbouncer/patroni | Foundations |
Gitaly | Durability |
CI Runners | Observability |
Gameday | Team |
---|
HAproxy | DB Operations |
pgbouncer/patroni | Runway |
Gitaly | Delivery: Release |
CI Runners | Delivery: Deployments |