You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- When writing a new entry to the updated table with a new column, version X doesn't know about new columns and will omit them from INSERT statements.
22
22
> [!NOTE]
23
23
> These columns need a database default or allow `NULL`
24
-
25
-
4. Canary pod with Version X+1 starts. It is running the same time as all the Version X pods.
26
-
5. Kubernetes rollout of Version X+1 starts:
24
+
4. Kubernetes rollout of Version X+1 starts:
27
25
- New pod with Version X+1 starts.
28
26
- When the Version X+1 pod is running, the Version X pod is shut down. This continues until no pods run Version X.
29
-
6. Version X+1 code is happily running in several pods.
27
+
5. Version X+1 code is happily running in several pods.
30
28
> [!WARNING]
31
29
> Misaligned code and database happens in Step 3 when Version X adds a new entry to the table without proper default set. In Step 6, the Version X+1 retrieves the entry. The fetched entry added by Version X does not meet the field validation in Version X+1 causing validation error.
32
30
@@ -46,11 +44,10 @@ Like adding a new field in an existing model, when deleting an existing model or
46
44
- Meanwhile the column remains in the database.
47
45
> [!NOTE]
48
46
> When writing to an existing table, version X should not refer to deleted columns.
49
-
4. Canary pod with Version X+1 starts. It is running the same time as all the Version X pods.
50
-
5. Kubernetes rollout of Version X+1 starts:
47
+
4. Kubernetes rollout of Version X+1 starts:
51
48
- New pod with Version X+1 starts.
52
49
- When the Version X+1 pod is running, the Version X pod is shut down. This continues until no pods run Version X.
53
-
6. Version X+1 code is happily running in several pods.
50
+
5. Version X+1 code is happily running in several pods.
54
51
> [!WARNING]
55
52
> Error happens when Version X or Version X+1 code refers to the deleted column.
Copy file name to clipboardExpand all lines: docs/release_process.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,8 @@
2
2
3
3
## Environments
4
4
5
-
-[Production][prod] - Run by SRE team in GCP
6
-
-[Stage][stage] - Run by SRE team in GCP
5
+
-[Production][prod] - Run by ENGR team in GCP
6
+
-[Stage][stage] - Run by ENGR in GCP
7
7
-[Dev][dev] - Run by ENGR team in MozCloud
8
8
- Locals: Run by ENGRs on their own devices. (See [README][readme] and other [`docs/`][docs].)
9
9
@@ -180,12 +180,13 @@ On Tuesday, after the Release Readiness review with QA:
180
180
181
181
1. Use the [release workflow][release-workflow] to select the tag and deploy
182
182
to the [Prod][prod] environment by selecting `prod`.
183
-
2. When you see `Application relay... is now running new version of deployments manifests.` in `#fx-private-relay-eng` on Slack, do some checks on prod:
183
+
2. Once the GitHub action finishes- go to ArgoCD an click "Sync" in the production application.
184
+
3. When you see `Application relay... is now running new version of deployments manifests.` in `#fx-private-relay-eng` on Slack, do some checks on prod:
184
185
- Spot-check the site for basic functionality
185
186
- Check [sentry prod project](https://mozilla.sentry.io/releases/?environment=prod) for a spike in any new issues
186
187
- Check [grafana dashboard](https://yardstick.mozilla.org/) for any unexpected spike in ops
187
188
- (optional) [Run the relay-only e2e test suite](https://github.com/mozilla/fx-private-relay/actions/workflows/playwright.yml) on prod
0 commit comments