Conversation
✅ Deploy Preview will be available once build job completes!
|
| | debug_points | NGINXaaS does not provide access to NGINX processes for debugging. | | ||
| | fastcgi_bind <br /> grpc_bind <br /> memcached_bind <br /> proxy_bind <br /> scgi_bind <br /> uwsgi_bind | Source IP specification for active-active deployments is not allowed. | | ||
| | quic_bpf | QUIC connection migration is not currently supported for active-active deployments. | | ||
| | ssl_ech_file | NGINXaaS does not use the OpenSSL ECH feature branch. | |
There was a problem hiding this comment.
the reasoning in itself is slightly vague. Maybe add a link to the directive which has that support statement and links to the ECH branch
| ## July 20, 2026 | ||
| NGINXaaS is now running NGINX Plus 37.0 (PLS.37.0). | ||
|
|
||
| NGINXaaS for Google Cloud deployments have been automatically upgraded to NGINX Plus 37.0 (PLS.37.0). Please review the [NGINX Plus Release 37.0]({{< ref "/nginx/releases/#pls.37.0.2" >}}) Release Notes carefully. Please note that HTTP/1.1 is now the default protocol for upstreams, and keepalive is enabled by default for HTTP/1.1 upstreams. Additionally, due to the new upstream histogram metric, zone memory requirements have increased by 25%. |
There was a problem hiding this comment.
- Is that increase in zone requirement permanent or is there a way, i.e., a customer always has to do so or is there a way to turn off that behavior?
- Do we have official documentation from NGINX as well around it?
- What happens if a customer does not follow the zone requirement guidance and goes with it anyway? do they get errors, does their traffic still work or prone to hit those errors?
There was a problem hiding this comment.
https://github.com/nginx/documentation/pull/2121/changes based on this PR, it looks like the customer always has to do so .
|
|
||
| NGINXaaS for Google Cloud deployments have been automatically upgraded to NGINX Plus 37.0 (PLS.37.0). Please review the [NGINX Plus Release 37.0]({{< ref "/nginx/releases/#pls.37.0.2" >}}) Release Notes carefully. Please note that HTTP/1.1 is now the default protocol for upstreams, and keepalive is enabled by default for HTTP/1.1 upstreams. Additionally, due to the new upstream histogram metric, zone memory requirements have increased by 25%. | ||
|
|
||
| NGINX Plus 37.0 (PLS.37.0) introduces new configuration directives and changes to existing directives. NGINXaaS for Google Cloud does not support the `ssl_ech_file` directive. For more information, review the unsupported directives listed in [Disallowed configuration directives]({{< ref "/nginxaas/google/deploy/nginx-configuration/overview/#disallowed-configuration-directives" >}}). |
There was a problem hiding this comment.
As I am reading through this doc and https://docs.nginx.com/nginx/releases/#intro, a question comes up on what a user will get as part of NGINXaaS. Is it the LTS release or CR model?
There was a problem hiding this comment.
Added LTS as part of the title
There was a problem hiding this comment.
Pull request overview
This PR updates the F5 NGINXaaS for Google Cloud documentation to announce the NGINX Plus 37.0 upgrade and align the documented directive support lists with new/changed directives introduced in that release.
Changes:
- Add a July 2026 changelog entry announcing the upgrade to NGINX Plus 37.0 and noting related behavioral changes.
- Mark
ssl_ech_fileas disallowed and adderror_log_tag/max_headersto the supported directives list. - Reformat several existing region tables/lists in the changelog for cleaner Markdown rendering.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| content/nginxaas/google/deploy/nginx-configuration/overview.md | Updates directive support documentation for NGINX Plus 37.0 (adds ssl_ech_file disallow + new directive links). |
| content/nginxaas/google/changelog.md | Adds the NGINX Plus 37.0 release announcement and normalizes formatting in older entries. |
Proposed changes
Announce NGINX Plus 37 availability and update directives list
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩