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
go run github.com/dadav/helm-schema/cmd/helm-schema@$(HELM_SCHEMA_VERSION) --chart-search-root=charts --add-schema-reference "--skip-auto-generation=required,additionalProperties" --append-newline
166
166
167
167
.PHONY: generate-all
168
-
generate-all: generate generate-crds generate-helm-schema generate-manifests generate-api-docs generate-helm-docs ## Generate all the necessary files
168
+
generate-all: generate generate-crds generate-helm-schema generate-manifests generate-api-docs generate-helm-docs verify-operator-rbac ## Generate all the necessary files
169
+
170
+
.PHONY: verify-operator-rbac
171
+
verify-operator-rbac: ## Verify operator RBAC is in sync with Helm chart
Copy file name to clipboardExpand all lines: docs/developer/release-process.md
+19-7Lines changed: 19 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,22 +69,34 @@ To create a new release, follow these steps:
69
69
- Build NGF, NGINX and NGINX Plus container images with the release tag `X.Y.Z` and push them to the registries.
70
70
- Package and publish the Helm chart to the registry.
71
71
- Create a GitHub release with an autogenerated changelog and attached release artifacts.
72
-
7. Prepare and merge a PR into the main branch to update with similar information that you did in the release branch docs PR. Specifically:
72
+
- Automatically submit UBI images for RedHat certification: The NGF, NGINX, and Operator UBI images are automatically submitted to the RedHat Partner Portal for preflight certification.
73
+
7. Operator Bundle Generation:
74
+
- You can generate and submit the operator bundle by running the [Operator Bundle PR workflow](https://github.com/nginx/nginx-gateway-fabric/actions/workflows/operator-bundle-pr.yml) with the following inputs:
75
+
- Set `operator-version` to the operator version (e.g., `1.0.1`, without the `v` prefix)
76
+
- Set `submit-to-redhat` to `true` if you want to automatically open a PR to the [RedHat certified-operators repository](https://github.com/redhat-openshift-ecosystem/certified-operators)
77
+
- This workflow will:
78
+
- Generate the operator bundle manifests using image digests
79
+
- Create a draft PR in the NGF repository with the bundle changes
80
+
- If `submit-to-redhat` is enabled, automatically fork and open a PR to the RedHat certified-operators repo
81
+
- Review and merge the internal bundle PR once approved
82
+
- Monitor the RedHat certified-operators PR for review feedback
83
+
8. Prepare and merge a PR into the main branch to update with similar information that you did in the release branch docs and operator bundle PRs. Specifically:
73
84
1.[README](/README.md) to include the information about the latest release.
74
85
2.[changelog](/CHANGELOG.md).
75
86
3. Helm chart `version` field.
76
87
4.`GW_API_PREV_VERSION` in tests Makefile, if necessary.
77
88
5. Any references in the docs to the previous release.
78
89
6. Any installation instructions to ensure that the supported Gateway API and NGF versions are correct. Specifically, helm README.
79
-
8. Prepare and merge a PR into the main branch of the [documentation repository](https://github.com/nginx/documentation) from the relevant release branch, such as `ngf-release-2.0`.
90
+
7. The operator bundle changes.
91
+
9. Prepare and merge a PR into the main branch of the [documentation repository](https://github.com/nginx/documentation) from the relevant release branch, such as `ngf-release-2.0`.
80
92
- In the NGF repo, run `make generate-api-docs` and copy the generated file from `docs/api/content.md` into the documentation repo to `content/ngf/reference/api.md`.
81
93
- Update the HTML file located at `layouts/shortcodes/version-ngf.html` with the latest version. Ensure you do not add an empty line to the file.
82
94
- Documentation is built and deployed automatically from `main`, and will trigger when merging to it.
83
95
- Create a new branch for the next release version, in the format `ngf-release-<i>.<i>`, substituting the *i* placeholders for major and minor version numbers.
84
-
9. Close the issue created in Step 1.
85
-
10. Ensure that the [associated milestone](https://github.com/nginx/nginx-gateway-fabric/milestones) is closed.
86
-
11. Verify that published artifacts in the release can be installed properly.
87
-
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).
96
+
10. Close the issue created in Step 1.
97
+
11. Ensure that the [associated milestone](https://github.com/nginx/nginx-gateway-fabric/milestones) is closed.
98
+
12. Verify that published artifacts in the release can be installed properly.
99
+
13. 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).
88
100
- Create a fork of the repository
89
101
- Name the file based on the requirements of the [README](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/reports/README.md). Update the README in the ngf directory and update the site source if necessary (see following example).
90
102
- Open a PR. [Example](https://github.com/kubernetes-sigs/gateway-api/pull/3149)
@@ -105,5 +117,5 @@ To create a new release, follow these steps:
105
117
branch.
106
118
4. Test the release branch for release-readiness.
107
119
5. If a problem is found, return to Step 2.
108
-
6. Follow Steps 5-7 from the [Major or Minor Release](#major-or-minor-release) section.
120
+
6. Follow Steps 5-8 from the [Major or Minor Release](#major-or-minor-release) section.
109
121
7. Prepare and merge a PR into the main branch of the [documentation repository](https://github.com/nginx/documentation) to update the NGF version in `layouts/shortcodes/version-ngf.html`. If any of our APIs have changed, in the NGF repo, run `make generate-api-docs` and copy the generated file from `docs/api/content.md` into the documentation repo to `content/ngf/reference/api.md`.
0 commit comments