Skip to content

release: push gateway chart 0.3.4 #8126

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
brow merged 2 commits into from
Oct 6, 2026
Merged

release: push gateway chart 0.3.4 #8126

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7f1f80a
release: push gateway chart 0.3.4
brow Oct 6, 2026
4f90575
docs: retain prior gateway chart release notes
brow Oct 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions deploy/charts/buzz-push-gateway/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,27 @@
# Chart release notes

## 0.3.4

Adds runtime Pod labels, a service account name, and a configurable termination
grace period of at least 60 seconds. Reserved selector labels cannot be overridden.

Allows a platform to replace the runtime NetworkPolicy by explicitly naming its
replacement. External policy mode supports PodMonitor without requiring unused
chart-owned monitoring selectors or APNs destinations. The complete-render gate
requires exactly one ordinary replacement NetworkPolicy
in the effective release namespace, selecting the runtime Pods and declaring
both ingress and egress policy types. Helm and Argo CD hook policies are rejected.
External-policy callers must supply independent Deployment, policy and namespace
expectations so removed or overwritten markers fail closed. The gate validates
selector expression grammar and expands Kubernetes Lists. Operators must validate
the full parent render including hooks; a Helm 3 post-renderer alone is insufficient.

Migration NetworkPolicy remains chart-owned and continues to require database
and DNS destinations. Runtime settings do not change migration Pod identity.
Default runtime rendering is unchanged.

Implemented in [#8113](https://github.com/block/buzz/pull/8113).

## 0.3.3

`gatewayOrigin` is now only an HTTPRoute routing input. It is optional unless
Expand Down
Loading