feat: Add proxy-busy-buffers-size to NIC
#916
Closed
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
* fixed the Service Mesh and ACM EoS banners * bolded SM EoS date
Add a NGF permissions document so that users can see what the security context of NGF is and what permissions it requires. Problem: Users don't know about NGF security and permissions. Solution: I added a permissions document that helps with that.
* feat: Integration steps: NAP-WAF into NGINX One Console - Basic transparant v. blocking policies - Strict policy - Adjustments - API info - Changelog Co-authored-by: yar <[email protected]> Apply suggestions from code review Co-authored-by: Daniel Edgar <[email protected]> Apply suggestions from code review * Update changelog release date
* feature: incorporate NIC and NGF into NGINX 1 Console * Include changelog Co-authored-by: Alan Dooley <[email protected]> Co-authored-by: Jodie Putrino <[email protected]> Co-authored-by: Travis Martin <[email protected]> Co-authored-by: Sylvia Wang <[email protected]> --------- Co-authored-by: Sylvia Wang <[email protected]>
* Update closed-contributions.md based on user testing * Update documentation/closed-contributions.md Co-authored-by: Mike Jang <[email protected]> --------- Co-authored-by: Alan Dooley <[email protected]>
* docs: update N1 config sync steps for v3 * docs: fix label * docs: fix tabs names
…#826) * added list of acronyms that don't need to be spelled out
Bump NIC Helm and Helm operator to latest patch release
Co-authored-by: Alan Dooley <[email protected]>
* feat: add list of NGINX alerts in XC --------- Co-authored-by: Travis Martin <[email protected]>
…833) * docs: update blocked ports list for NGINXaaS Azure listen directive and remove port usage details.
Be explicit about the use of the Preview channel in the NGINX 4 azure docs We implicitly imply that the preview channel should not be used for production environments but listing the environments it SHOULD be used for. This change makes it explicit.
* chore: Removed unneeded isFeatured param for cards, replaced with isFullSize
chore: Update on mainframe the correct url for Unit
chore: Bump theme version to v0.43.6
fix: Update N1 landing page images
* fix: update N1 Console index page * Reorg boxes * Update content/nginx-one/_index.md Co-authored-by: Travis Martin <[email protected]> --------- Co-authored-by: Travis Martin <[email protected]>
feat: Add description to slack notification for new theme release
#848) fix: Resolved incorrect object name for the slack message in build workflow
…ere appropriate (#849) * fix: replace incorrect 'NGINX One' labels with 'NGINX One Console' where appropriate * Apply suggestion from @mjang Co-authored-by: Mike Jang <[email protected]> * Apply suggestion from @mjang Co-authored-by: Mike Jang <[email protected]> --------- Co-authored-by: Alan Dooley <[email protected]> Co-authored-by: Alan Dooley <[email protected]> Co-authored-by: Mike Jang <[email protected]>
* fix: Add Offline steps to install WAF compiler on NIM * fix: Update setup-waf-config-management.md * fix: Update content/nim/nginx-app-protect/setup-waf-config-management.md Co-authored-by: Travis Martin <[email protected]> * fix: Update content/nim/nginx-app-protect/setup-waf-config-management.md Co-authored-by: Travis Martin <[email protected]> * fix: Update content/nim/nginx-app-protect/setup-waf-config-management.md Co-authored-by: Travis Martin <[email protected]> * fix: Update content/nim/nginx-app-protect/setup-waf-config-management.md Co-authored-by: Travis Martin <[email protected]> * fix: Update content/nim/nginx-app-protect/setup-waf-config-management.md Co-authored-by: Travis Martin <[email protected]> * fix: Update content/nim/nginx-app-protect/setup-waf-config-management.md Co-authored-by: Travis Martin <[email protected]> * fix: Update content/nim/nginx-app-protect/setup-waf-config-management.md Co-authored-by: Travis Martin <[email protected]> * fix: Update content/nim/nginx-app-protect/setup-waf-config-management.md Co-authored-by: Travis Martin <[email protected]> * fix: Update content/nim/nginx-app-protect/setup-waf-config-management.md Co-authored-by: Travis Martin <[email protected]> --------- Co-authored-by: Travis Martin <[email protected]>
This commit adds OpenTelemetry documentation for NGINX Ingress Controller, converting an example hidden in the code repository. It adds it to the "Logging and monitoring" section, where the prior OpenTracing document has also been moved. The latter document has had an explicit warning call-out added to the top directing users to the new document, and the release page now links directly to the new configuration document for context. Some page titles and metadata in the section have also been updated as part of this work, to ensure the user experience is more consistent. Co-authored-by: yar <[email protected]>
* Add specific version instructions for NGINX Agent v2 installation * Remove lsb_release from instructions, use code name instead Remove comma based on PR feedback
fix: s/upgrade/update as needed
chore: Remove unneeded span on getting started for N1
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.29.2 to 3.29.4. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@181d5ee...4e828ff) --- updated-dependencies: - dependency-name: github/codeql-action dependency-version: 3.29.4 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Update tech specs
* Include JWT license reference to installing-nginx-docker.md --------- Co-authored-by: yar <[email protected]> Co-authored-by: Alessandro Fael Garcia <[email protected]>
This commit updates the Hugo guidance to accurately reflect the usage of our most common shortcodes, and guides people away from the ones that have been removed or will be removed soon based on Mainframe changes. The guidance is not fully inclusive: we have not yet determined where full documentation for all theme elements should live (Such as a publicly-facing design system), but it should cover the most commonly used shortcodes. The pull request template has also been updated in the same manner, attempting to focus on critical information for contributors. The checklist was previously quite long: it has been reduced to essential elements, and reframed as a direct, personal commitment. The detail underneath the "Proposed changes" has been shifted to inline, hidden guidance, following a similar pattern in our Hugo archetypes. Some information from the old checklist has been moved there, but it otherwise covers the same ground as the old guidance. It refers to and reinforces our standards asserted by our Git conventions documentation, and will not create visual noise within the PR should the contributor choose not to remove it.
#816) This commit makes a number of changes to clarify what the precise steps are to install, upgrade and uninstall NGINX Ingress Controller - The Install document clarifies necessary steps - Uninstall steps have been moved to the bottom of the document - Upgrade instructions have been moved into their own document The changes made focused on clarifying the critical path for one single user story, as lots of unnecessary contextual information was being provided, which was causing confusion. With this commit, the general reading and execution flow for these deployment steps become more coherent. Similar changes may be made for Manifests documentation, if common steps are identified. As part of the work, a number of include files have been updated or created that are shared with NGINX Plus, to ensure the documentation around obtaining an NGINX Ingress Controller image with Docker are consistent. Subsequently, process documentation for managing includes was split from the style guide and made into its own file due to the anticipated length as reference information. --------- Co-authored-by: Travis Martin <[email protected]>
* Update docker connect to N1C command * Update content/nginx-one/connect-instances/connect-nginx-plus-container-images-to-nginx-one.md --------- Co-authored-by: Alan Dooley <[email protected]>
…492) Moved content to incldues
* fix: expose Agent config options
…rom NIC (#914) update manifest instructions to enable NAP security monitoring from NIC
Relative links seem broken in the template. Replacing with absolute links
* docs: update supported OS's and compatibility, remove freebsd agent support
github-actions
bot
added
documentation
✅ Deploy Preview will be available once build job completes!
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
23 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
proxy-busy-buffers-sizeto ConfigMapnginx.org/proxy-busy-buffers-sizeto Ingress Annotationsbusy-buffers-sizeto VirtualServernginx.org/proxy-busy-buffers-sizeChecklist
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. ↩