feat: Add F5 WAF bundle source polling to NGINX Ingress Controller#2074
Open
AlexFenlon wants to merge 11 commits into
Open
feat: Add F5 WAF bundle source polling to NGINX Ingress Controller#2074AlexFenlon wants to merge 11 commits into
AlexFenlon wants to merge 11 commits into
Conversation
6 tasks
✅ Deploy Preview will be available once build job completes!
|
…into nic/waf-mgmt-bundle
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
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
This PR adds docs for F5 WAF for NGINX bundle sources in NGINX Ingress Controller 5.6.
add a new bundle-source tutorial for NGINX One Console, NGINX Instance Manager, and HTTPS.
Updates Policy docs for apBundleSource and apLogBundleSource fields, including polling and source-specific behavior.
Updates WAF v5 configuration/compile/troubleshooting pages with links and guidance for automated bundle fetch workflows.
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. ↩