generated from nginx/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 119
NGINX App Protect WAF 5.6 / 4.14 #280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
* feat: install nap 5 with helm chart * Update content/nap-waf/v5/admin-guide/deploy-on-kubernetes/deploy-with-helm.md Co-authored-by: Jon Torre <[email protected]>
✅ Deploy Preview will be available once build job completes!
|
liadlevif5
reviewed
Mar 13, 2025
content/nap-waf/v5/admin-guide/deploy-on-kubernetes/deploy-with-helm.md
Outdated
Show resolved
Hide resolved
content/nap-waf/v5/admin-guide/deploy-on-kubernetes/deploy-with-manifests.md
Outdated
Show resolved
Hide resolved
content/nap-waf/v5/admin-guide/deploy-on-kubernetes/deploy-with-helm.md
Outdated
Show resolved
Hide resolved
ohad-perets
reviewed
Mar 17, 2025
ADubhlaoich
commented
Mar 18, 2025
ohad-perets
reviewed
Mar 19, 2025
ohad-perets
reviewed
Mar 19, 2025
ohad-perets
reviewed
Mar 19, 2025
ohad-perets
reviewed
Mar 19, 2025
ohad-perets
reviewed
Mar 19, 2025
ohad-perets
reviewed
Mar 19, 2025
ohad-perets
reviewed
Mar 19, 2025
ohad-perets
reviewed
Mar 19, 2025
ohad-perets
reviewed
Mar 19, 2025
ohad-perets
reviewed
Mar 19, 2025
6 tasks
ohad-perets
reviewed
Mar 30, 2025
ohad-perets
reviewed
Mar 30, 2025
removing && from DanielK's comments
remove also for plus
dkleinF5
reviewed
Mar 30, 2025
ADubhlaoich
commented
Apr 1, 2025
remove mtls & read-only references due to a bug, need to fix that after release
ohad-perets
approved these changes
Apr 1, 2025
aknot242
reviewed
Apr 1, 2025
update login with jwt
aknot242
reviewed
Apr 1, 2025
mjang
approved these changes
Apr 1, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Posting as 2nd approval, as all comments have been addressed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Improvements or additions to documentation
product/waf
Issues related to F5 WAF for NGINX
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
This pull request covers the release of NGINX App Protect WAF 5.6 and 4.14.
It updates the release notes, and also begins the process of reducing noise from the documentation set by removing deprecated instructions and consolidating duplicate information.
Checklist
Before merging a pull request, run through this checklist and mark each as complete.
README.md
andCHANGELOG.md
Footnotes
Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩