-
Notifications
You must be signed in to change notification settings - Fork 108
Comparing changes
Open a pull request
base repository: nginx/nginx-gateway-fabric
base: v1.5.0
head repository: nginx/nginx-gateway-fabric
compare: v1.5.1
- 14 commits
- 82 files changed
- 9 contributors
Commits on Nov 21, 2024
-
Deploy docs for release 1.5.0 (#2800)
Deploy docs for release 1.5.0
Configuration menu - View commit details
-
Copy full SHA for b6954cb - Browse repository at this point
Copy the full SHA b6954cbView commit details
Commits on Nov 25, 2024
-
Skip plus tests on a fork (#2784) (#2816)
Problem: The NGINX Plus JWT is only available on the upstream repo, so automated tests for Plus can't be run on forks. Solution: Skip these test runs on a fork.
Configuration menu - View commit details
-
Copy full SHA for 4c1f7d3 - Browse repository at this point
Copy the full SHA 4c1f7d3View commit details -
Cherry pick recent documentation changes (#2815)
This commit cherry-picks changes from 3 recent documentation PRs from main to the 1.5 release branch. More specifically, the work in the following PRs: - Update support referencing support package tool #2789 - Docs: remove () typo from troubleshooting doc #2803 - Clear up installation language #2808 --------- Co-authored-by: Madhu Rajagopal <m.rajagopal@f5.com> Co-authored-by: Saylor Berman <s.berman@f5.com> Co-authored-by: nginx-aoife <50101789+nginx-aoife@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 4ad7473 - Browse repository at this point
Copy the full SHA 4ad7473View commit details
Commits on Nov 26, 2024
-
SnippetsFilter CRD missing from crds manifest (#2821) (#2822)
Problem: The SnippetsFilter CRD is missing from deploy/crds.yaml, which is used to install NGF with manifests. Solution: Add SnippetsFilter CRD to the kustomization file that is used to generate the deploy/crds.yaml file.
Configuration menu - View commit details
-
Copy full SHA for b3476f1 - Browse repository at this point
Copy the full SHA b3476f1View commit details
Commits on Nov 27, 2024
-
(cherry-pick) Update documentation action, bump version for local tes…
…ting (#2834) This commit bumps the theme version for the documentation website, and updates the GitHub action used for deploying the website. The update allows you to specify what version of the theme to use for a deployment, which reduces the drift compared to relying on the local version. Co-authored-by: bjee19 <139261241+bjee19@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 80b4d51 - Browse repository at this point
Copy the full SHA 80b4d51View commit details
Commits on Dec 5, 2024
-
Update NGF version in getting started document (#2870)
Update NGF version in getting started document
Configuration menu - View commit details
-
Copy full SHA for a890a8b - Browse repository at this point
Copy the full SHA a890a8bView commit details
Commits on Dec 9, 2024
-
feat: Update docs configuration for new logo (#2867) (#2880)
In a prior commit, the Hugo theme for the documentation was updated. With that update, the new logo for NGINX Gateway Fabric was made available (Previously used for Service Mesh). This commit makes the necessary configuration changes for the new logo to be available: there is a paired pull request for the main documentation website.
Configuration menu - View commit details
-
Copy full SHA for 1ebaa55 - Browse repository at this point
Copy the full SHA 1ebaa55View commit details
Commits on Dec 13, 2024
-
Cherry-pick N+ deployment context fix to release-1.5 (#2905)
Write deployment context in init container (#2871) Problems: * When running with N+, the first usage report does not contain the deployment context. The deployment context is needed in order to associate the instance with NGF. * When collecting the info for the deployment context, it is possible to fail. In this case we send a report to N1 without the deployment context. * The installation ID is the deployment ID, but it should be the Pod ID. Solutions: * When running with N+, write the deployment context to the shared volume mount in the init container. * Use the Pod UID instead of the deployment UID as the installation ID * Always set the static values of the deployment context in the nginx config. Static values include the integration and installation IDs.
Configuration menu - View commit details
-
Copy full SHA for a5e94c2 - Browse repository at this point
Copy the full SHA a5e94c2View commit details -
Use staging endpoint for N+ reporting in pipeline (#2885) (#2907)
Problem: Pipeline uses production endpoint for N+ usage reporting, which should be reserved for production deployments. Solution: Use staging endpoint in the pipeline. Devs will need to export the staging endpoint in their environments in order to run the NFR, functional, and conformance tests locally.
Configuration menu - View commit details
-
Copy full SHA for 2ce993f - Browse repository at this point
Copy the full SHA 2ce993fView commit details -
Configuration menu - View commit details
-
Copy full SHA for e153640 - Browse repository at this point
Copy the full SHA e153640View commit details -
Omit empty deployment context fields (#2903) (#2910)
Problem: If an optional deployment context field wasn't set, an empty value would still be sent and cause the reporting server to return a 400. Solution: Use pointers on the optional fields to omit them from the context if they're empty.
Configuration menu - View commit details
-
Copy full SHA for 9c2deea - Browse repository at this point
Copy the full SHA 9c2deeaView commit details -
Move check for plus usage endpoint to test-with-plus target (#2902) (#…
Configuration menu - View commit details
-
Copy full SHA for 955af30 - Browse repository at this point
Copy the full SHA 955af30View commit details
Commits on Dec 16, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 601f341 - Browse repository at this point
Copy the full SHA 601f341View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7b60982 - Browse repository at this point
Copy the full SHA 7b60982View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.5.0...v1.5.1