New NGF CLI parameter for Trial period enforcement #1128
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
documentation
|
✅ All required contributors have signed the F5 CLA for this PR. Thank you! |
✅ Deploy Preview will be available once build job completes!
|
tataruty
force-pushed
the
doc/enforce_initial_report_for_plus_trial
branch
from
fcd1795 to
9ff7095
Compare
|
I have hereby read the F5 CLA and agree to its terms |
sjberman
approved these changes
Sep 16, 2025
bjee19
pushed a commit
to bjee19/documentation
that referenced
this pull request
Oct 22, 2025
ciarams87
added a commit
that referenced
this pull request
Oct 22, 2025
* Update compability doc (#1054) Update compatability doc with Port for ParentRef * NGF: Update gateway addresses compatibility document (#1109) Update gateway addresses compatibility document. * NGF: Update gateway addresses compatibility document with IP family comment (#1126) Add a small comment on IP families to gateway addresses compatibility document. * New NGF CLI parameter for Trial period enforcement (#1128) * RouteRules and Gateway unsupported fields update (#1268) Added mention about unsupported fields for RouteRules and Gateways Closes nginx/nginx-gateway-fabric#3784 * NGF: Update advanced routing guide for Regex PathType (#1286) feat: Update advanced routing guide for regex path * Add details on BuildOS and InferencePoolCount to Product Telemetry docs (#1284) * Add details on BuildOS and InferencePoolCount to Product Telemetry docs * Add InferencePoolCount * Move InferencePool resource into "Count of Resources" section * Chore: Update api docs and version for release --------- Co-authored-by: Sarthak Agrawal <[email protected]> Co-authored-by: bjee19 <[email protected]> Co-authored-by: Tina U. <[email protected]> Co-authored-by: Alan Dooley <[email protected]> Co-authored-by: Shaun <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
NGF currently sets enforce_initial_report off; for NGINX Plus data planes when initially installing.
Users should be able to set this field themselves for other circumstances, like PoC testing or exemptions.
For reference: https://nginx.org/en/docs/ngx_mgmt_module.html#enforce_initial_report
Related task: nginx/nginx-gateway-fabric#3790
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. ↩