generated from nginx/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 120
feat: WAF PLM Overview and Installation (#1060) #1077
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
* PLM Overview and Installation * fix: remove redundant section * fix: MR comments * chore: added doc dor new directive
✅ Deploy Preview will be available once build job completes!
|
* ApSignatures * fix: new line
chore: add upgrade/uninstall steps for PLM
* WAFMC-13048-offline-solution-for-APSignature * fix: doc offline solution for APSignatures
* Update PLM Installation Section * fix: namespace * fix: namespace values.yaml * fix: namespace instructions * fix: remove unneeded line * fix: release name * fix: missing pvc in values.yaml * fix: missing values.yaml content * fix: correct dockerfile * fix: missing values.yaml sections * fix: clarify verify output * fix: clarifications * fix: sudo * fix: 5.9.0 * fix: typo * fix: clarify cert and key files * fix: test policy clarification * fix: edit nginx.conf * fix: clarify configuration * fix: pv yaml indent * fix: values.yaml * fix: clarifications * fix: missing set args * fix: helm upgrade * fix: after rebase
mjang
approved these changes
Sep 22, 2025
y82
reviewed
Sep 23, 2025
| ``` | ||
|
|
||
| {{< call-out "note" >}} | ||
| **NGINX Repository Credentials**: Replace `/path/to/your/nginx-repo.crt` and `/path/to/your/nginx-repo.key` with the actual paths to your NGINX repository certificate and key files. These are typically provided by NGINX when you get access to the private registry. The files may have similar names like `nginx-repo.crt` and `nginx-repo.key` or `nginx.crt` and `nginx.key`. |
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.
This is not quite correct:
1- crt and key files are downloaded from your account on myF5
2 - the file name you download is nginx-repo-H-abcd1234.crt
3. - you will need to rename the crt and key files to nginx-repo.crt and nginx-repo.key in order to have access
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
Full description TBD
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. ↩