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
Problem: NGF does not set the SupportedVersion condition
on the GatewayClass.
Solution: Set the SupportedVersion condition on the GatewayClass.
This PR adds a new controller that watches the metadata of CRDs.
CRD events are filtered using a custom predicate that inspects the
gateway.networking.k8s.io/bundle-version annotation. CRDs without
this annotation will be ignored. Updates to this annotation will trigger
a state change and build a new graph. This required some changes to
how we determine if the state has changed in the changeTrackingUpdater.
Copy file name to clipboardExpand all lines: docs/developer/release-process.md
+12-10
Original file line number
Diff line number
Diff line change
@@ -30,8 +30,10 @@ To create a new release, follow these steps:
30
30
3. Test the main branch for release-readiness. For that, use the `edge` containers, which are built from the main
31
31
branch, and the [example applications](/examples).
32
32
4. If a problem is found, prepare a fix PR, merge it into the main branch and return to the previous step.
33
-
5. Create a release branch with a name that follows the `release-X.Y` format.
34
-
6. Prepare and merge a PR into the release branch to update the repo files for the release:
33
+
5. If the supported Gateway API minor version has changed since the last release, test NGINX Gateway Fabric with the previous version of the Gateway API CRDs.
34
+
6. If a compatibility issue is found, add a note to the release notes explaining that the previous version is not supported.
35
+
7. Create a release branch following the `release-X.Y` naming convention.
36
+
8. Prepare and merge a PR into the release branch to update the repo files for the release:
35
37
1. Update the Helm [Chart.yaml](/deploy/helm-chart/Chart.yaml): the `appVersion` to `X.Y.Z`, the icon and source
36
38
URLs to point at `vX.Y.Z`, and bump the `version`.
37
39
2. Adjust the `VERSION` variable in the [Makefile](/Makefile) and the `TAG` in the
@@ -52,17 +54,17 @@ To create a new release, follow these steps:
52
54
draft of the full changelog. This draft can be found under
53
55
the [GitHub releases](https://github.com/nginxinc/nginx-gateway-fabric/releases) after the release branch is
54
56
created. Use the previous changelog entries for formatting and content guidance.
55
-
7. Create and push the release tag in the format `vX.Y.Z`. As a result, the CI/CD pipeline will:
57
+
9. Create and push the release tag in the format `vX.Y.Z`. As a result, the CI/CD pipeline will:
56
58
- Build NGF container images with the release tag `X.Y.Z` and push it to the registry.
57
59
- Package and publish the Helm chart to the registry.
58
60
- Create a GitHub release with an autogenerated changelog and attached release artifacts.
59
-
8. Prepare and merge a PR into the main branch to update the [README](/README.md) to include the information about
60
-
the latest release and also the [changelog](/CHANGELOG.md). Also update any installation instructions to ensure
61
-
that the supported Gateway API and NGF versions are correct. Specifically, helm README and `site/content/includes/installation/install-gateway-api-resources.md`.
62
-
9. Close the issue created in Step 1.
63
-
10. Ensure that the [associated milestone](https://github.com/nginxinc/nginx-gateway-fabric/milestones) is closed.
64
-
11. Verify that published artifacts in the release can be installed properly.
65
-
12. Submit the `conformance-profile.yaml` artifact from the release to the [Gateway API repo](https://github.com/kubernetes-sigs/gateway-api/tree/main/conformance/reports).
61
+
10. Prepare and merge a PR into the main branch to update the [README](/README.md) to include the information about
62
+
the latest release and also the [changelog](/CHANGELOG.md). Also update any installation instructions to ensure
63
+
that the supported Gateway API and NGF versions are correct. Specifically, helm README and `site/content/includes/installation/install-gateway-api-resources.md`.
64
+
11. Close the issue created in Step 1.
65
+
12. Ensure that the [associated milestone](https://github.com/nginxinc/nginx-gateway-fabric/milestones) is closed.
66
+
13. Verify that published artifacts in the release can be installed properly.
67
+
14. Submit the `conformance-profile.yaml` artifact from the release to the [Gateway API repo](https://github.com/kubernetes-sigs/gateway-api/tree/main/conformance/reports).
66
68
- Create a fork of the repository
67
69
- Name the file `nginxinc-nginx-gateway-fabric.yaml` and set `gatewayAPIVersion` in the file to the
68
70
supported version by NGF. Also update the site source if necessary (see following example).
0 commit comments