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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+29Lines changed: 29 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,35 @@ This document includes a curated changelog for each release. We also publish a c
4
4
a [GitHub release](https://github.com/nginx/nginx-gateway-fabric/releases), which, by contrast, is auto-generated
5
5
and includes links to all PRs that went into the release.
6
6
7
+
## Release 2.0.1
8
+
9
+
_June 11, 2025_
10
+
11
+
Bug Fixes:
12
+
13
+
- Set proper IP family policy on NGINX LB Service. [3475](https://github.com/nginx/nginx-gateway-fabric/pull/3475).
14
+
15
+
HELM CHART:
16
+
17
+
- The version of the Helm chart is now 2.0.1.
18
+
- Add support to configure `cert-generator` job pod placement. [3493](https://github.com/nginx/nginx-gateway-fabric/pull/3493). Thanks to [Baburciu](https://github.com/baburciu).
19
+
- Add support for configuring the `ttlSecondsAfterFinished` field for the cert-generator job. The default is set to 30s. [3487](https://github.com/nginx/nginx-gateway-fabric/pull/3487). Thanks to [Ab-andresc](https://github.com/ab-andresc).
20
+
- Adds support for all additional labels for the control plane service. [3499](https://github.com/nginx/nginx-gateway-fabric/pull/3499). Thanks to [MichasHL](https://github.com/michasHL).
21
+
22
+
COMPATIBILITY:
23
+
24
+
- Gateway API version: `1.3.0`
25
+
- NGINX version: `1.28.0`
26
+
- NGINX Plus version: `R34`
27
+
- NGINX Agent version: `v3.0.1`
28
+
- Kubernetes version: `1.25+`
29
+
30
+
CONTAINER IMAGES:
31
+
32
+
- Control plane: `ghcr.io/nginx/nginx-gateway-fabric:2.0.1`
33
+
- Data plane: `ghcr.io/nginx/nginx-gateway-fabric/nginx:2.0.1`
34
+
- Data plane with NGINX Plus: `private-registry.nginx.com/nginx-gateway-fabric/nginx-plus:2.0.1`
| Latest release | For production use |[Manifests](https://github.com/nginx/nginx-gateway-fabric/tree/v2.0.0/deploy). |[Documentation](https://docs.nginx.com/nginx-gateway-fabric). [Examples](https://github.com/nginx/nginx-gateway-fabric/tree/v2.0.0/examples). |
50
+
| Latest release | For production use |[Manifests](https://github.com/nginx/nginx-gateway-fabric/tree/v2.0.1/deploy). |[Documentation](https://docs.nginx.com/nginx-gateway-fabric). [Examples](https://github.com/nginx/nginx-gateway-fabric/tree/v2.0.1/examples). |
51
51
| Edge | For experimental use and latest features |[Manifests](https://github.com/nginx/nginx-gateway-fabric/tree/main/deploy). |[Examples](https://github.com/nginx/nginx-gateway-fabric/tree/main/examples). |
52
52
53
53
### Versioning
@@ -68,7 +68,8 @@ The following table lists the software versions NGINX Gateway Fabric supports.
68
68
69
69
| NGINX Gateway Fabric | Gateway API | Kubernetes | NGINX OSS | NGINX Plus | NGINX Agent |
Copy file name to clipboardExpand all lines: docs/developer/release-process.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,15 @@ To create a new release, follow these steps:
54
54
the [GitHub releases](https://github.com/nginx/nginx-gateway-fabric/releases) after the release branch is
55
55
created. If included, use the Release Notes specified in a PR.
56
56
- If the supported Gateway API minor version has changed since the last release, add a note to the release notes explaining if the previous version is no longer supported.
57
-
6. Ensure you are on the latest version of the release branch and are up-to-date on all commits, then create and push the release tag in the format `vX.Y.Z`. As a result, the CI/CD pipeline will:
57
+
- Merge the release PR once it has received all necessary approvals.
58
+
6. Ensure you are on the latest version of the release branch and are up-to-date on all commits, then create and push the release tag in the format `vX.Y.Z`.
59
+
60
+
```shell
61
+
git tag vX.Y.Z
62
+
git push upstream vX.Y.Z
63
+
```
64
+
65
+
As a result, the CI/CD pipeline will:
58
66
- Build NGF, NGINX and NGINX Plus container images with the release tag `X.Y.Z` and push them to the registries.
59
67
- Package and publish the Helm chart to the registry.
60
68
- Create a GitHub release with an autogenerated changelog and attached release artifacts.
0 commit comments