F5 WAF for NGINX 5.9 #949
Draft
F5 WAF for NGINX 5.9 #949
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
the
documentation
✅ Deploy Preview will be available once build job completes!
|
4 tasks
github-actions
bot
added
the
tooling
This commit adds an initial entry to the policy configuration section, covering the information around attack signatures. Previously the instructions and reference information were available separately on the same page, which I have now grouped together logically. I'm not entirely convinced this will remain the best possible layout, but it works as an MVP for a vertical slice.
github-actions
bot
added
the
product/nim
ohad-perets
reviewed
Sep 25, 2025
|
|
||
| ## Use Policy lifecycle management | ||
|
|
||
| ### Create policy resources |
There was a problem hiding this comment.
Create Policy custom resources
ohad-perets
reviewed
Sep 25, 2025
| In totality, you should see the following: | ||
|
|
||
| - **Policy Controller pod**: `1/1 Running` status | ||
| - **F5 WAF for NGINX pod**: `4/4 Running` status (nginx, waf-config-mgr, waf-enforcer, waf-ip-intelligence containers) |
There was a problem hiding this comment.
need to add a note that if IPI is installed, you will have 4, else only 3
ohad-perets
reviewed
Sep 25, 2025
Comment on lines
+802
to
+807
| - **`status.bundle.signatures`**: Timestamps showing when security signatures were last updated | ||
| - `attackSignatures` - Attack signature update timestamp | ||
| - `botSignatures` - Bot signature update timestamp | ||
| - `threatCampaigns` - Threat campaign signature update timestamp | ||
| - **`status.processing.isCompiled`**: Boolean indicating if compilation completed successfully | ||
| - **`status.processing.datetime`**: Timestamp of the last compilation attempt |
There was a problem hiding this comment.
Need to remove this section(duplication)see lines 795-800)
liadlevif5
reviewed
Sep 25, 2025
|
|
||
| ```shell | ||
| helm registry login private-registry.nginx.com | ||
| helm pull oci://private-registry.nginx.com/nap/nginx-app-protect --version <release-version> --untar |
There was a problem hiding this comment.
Suggested change
| helm pull oci://private-registry.nginx.com/nap/nginx-app-protect --version <release-version> --untar | |
| helm pull oci://private-registry.nginx.com/nap/nginx-app-protect --version 5.9.0-ea --untar |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Full detail TBD.
Includes
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. ↩