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: docs/developer/release-process.md
+3-2
Original file line number
Diff line number
Diff line change
@@ -30,15 +30,16 @@ 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 run the following:
32
32
1. Run the [example applications](/examples) manually and verify their correctness.
33
-
2. Kick off the [NFR workflow](https://github.com/nginxinc/nginx-gateway-fabric/actions/nfr.yml) in the browser. For `image_tag`, use `edge`, and for `version`, use the upcoming `X.Y.Z` NGF version. This will run all of the NFR tests which are automated and open a PR with the results files when it is complete. Review this PR and make any necessary changes before merging.
33
+
2. Kick off the [NFR workflow](https://github.com/nginxinc/nginx-gateway-fabric/actions/workflows/nfr.yml) in the browser. For `image_tag`, use `edge`, and for `version`, use the upcoming `X.Y.Z` NGF version. This will run all of the NFR tests which are automated and open a PR with the results files when it is complete. Review this PR and make any necessary changes before merging.
34
34
4. If a problem is found, prepare a fix PR, merge it into the main branch and return to the previous step.
35
35
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.
36
36
6. If a compatibility issue is found, add a note to the release notes explaining that the previous version is not supported.
37
37
7. Create a release branch following the `release-X.Y` naming convention.
38
-
8. Run the [Release PR](./../../.github/workflows/release-pr.yml) workflow to update the repo files for the release. Then there are a few manual steps to complete:
38
+
8. Run the [Release PR](https://github.com/nginxinc/nginx-gateway-fabric/actions/workflows/release-pr.yml) workflow to update the repo files for the release. Then there are a few manual steps to complete:
39
39
1. Update the tag of NGF container images used in the [provisioner manifest](/tests/conformance/provisioner/provisioner.yaml).
40
40
2. Update the [README](/README.md) to include information about the release.
41
41
3. Update the [changelog](/CHANGELOG.md). There is going to be a new blank section generated by the automation that needs to be adjusted accordingly.
42
+
At the top there will be a list of all PRs that are labeled with `release-notes`.
42
43
The changelog includes only important (from the user perspective)
43
44
changes to NGF. This is in contrast with the autogenerated full changelog, which is created in the next
44
45
step. As a starting point, copy the important features, bug fixes, and dependencies from the autogenerated
If a resource has errors relating to its configuration or relationship to other resources, they can likely be read in the status. The `ObservedGeneration` in the status should match the `ObservedGeneration` of the resource. Otherwise, this could mean that the resource hasn't been processed yet or that the status failed to update.
51
+
52
+
##### Events
53
+
54
+
Events created by NGINX Gateway Fabric or other Kubernetes components could indicate system or configuration issues. To see events:
55
+
56
+
```shell
57
+
kubectl get events [-n namespace]
58
+
```
59
+
60
+
For example, a warning event when the NginxGateway configuration CRD is deleted:
61
+
62
+
```text
63
+
kubectl -n nginx-gateway get event
64
+
LAST SEEN TYPE REASON OBJECT MESSAGE
65
+
5s Warning ResourceDeleted nginxgateway/ngf-config NginxGateway configuration was deleted; using defaults
66
+
```
67
+
68
+
##### Logs
69
+
70
+
Logs from the NGINX Gateway Fabric control plane and data plane can contain information that isn't available to status or events. These can include errors in processing or passing traffic.
0 commit comments