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
{{ message }}
Repository navigation
Commit a2aed2b
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/push-gateway-deployment.md
+14-3Lines changed: 14 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -224,7 +224,17 @@ gh attestation verify \
224
224
--source-digest <40-lowercase-hex-source-commit>
225
225
```
226
226
227
-
Only after that command succeeds, record the exact digest as `image.digest`; the chart then renders `ghcr.io/block/buzz-push-gateway@sha256:...` and ignores the mutable tag. The `0.2.0` production values pin `sha256:3936cad2d5cb0f6711c749024b96e56969d7e4506eb35d3519e3ef126fa6636d`, the amd64/arm64 index built from `4a9de1a3a121285ef475d630b2b5764044c02cde` by the successful [main image workflow](https://github.com/block/buzz/actions/runs/33457946099). Its SLSA provenance was verified against `block/buzz/.github/workflows/docker.yml` and that source digest. `values-production.yaml` remains an intentionally invalid production-input contract: deployment CI must inject the provisioned dogfood Apple application identifier and the actual PostgreSQL network. In an environment with an existing ingress or service mesh route, keep `httpRoute.enabled=false`. If this chart owns a Gateway API route, enable it and inject an environment-owned `parentRef`; schema validation rejects an enabled route with no parent. The render guard proves both rejection of missing required inputs and fully injected renders.
227
+
Only after that command succeeds, inject the exact digest as `image.digest` in
228
+
the environment's GitOps values; the chart then renders
229
+
`ghcr.io/block/buzz-push-gateway@sha256:...`and ignores the mutable tag.
230
+
`values-production.yaml`remains an intentionally invalid production-input
231
+
contract: deployment CI must inject the verified image digest, the provisioned
232
+
dogfood Apple application identifier, and the actual PostgreSQL network. In an
233
+
environment with an existing ingress or service mesh route, keep
234
+
`httpRoute.enabled=false`. If this chart owns a Gateway API route, enable it and
235
+
inject an environment-owned `parentRef`; schema validation rejects an enabled
236
+
route with no parent. The render guard proves both rejection of missing required
237
+
inputs and fully injected renders.
228
238
229
239
Network policy keeps APNs HTTPS and PostgreSQL egress in separate CIDR lists. APNs currently requires broad TCP/443 reachability; `networkPolicy.postgresEgressCidrs` must be narrowed to the production database network, and the DNS namespace/pod selectors must match the cluster DNS deployment. The sample private CIDR is not a claim about the production topology.
230
240
@@ -233,8 +243,9 @@ Kubernetes does not restart pods when referenced Secret bytes change. AEAD or AP
233
243
## Gateway chart release
234
244
235
245
The gateway chart has a collision-free release lane separate from the main
236
-
`buzz`chart. To publish version `X.Y.Z`, update both `version` and `appVersion`
237
-
in `deploy/charts/buzz-push-gateway/Chart.yaml`, validate the chart, and open a
246
+
`buzz`chart. To publish chart version `X.Y.Z`, update `version` in
247
+
`deploy/charts/buzz-push-gateway/Chart.yaml`and keep `appVersion` equal to the
248
+
gateway binary's workspace package version. Validate the chart, then open a
238
249
same-repository PR whose branch is exactly `push-chart-release/X.Y.Z`:
0 commit comments