-
Notifications
You must be signed in to change notification settings - Fork 125
feature: dos k8s / dos k8s with ebpf #1533
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview will be available once build job completes!
|
…into app-protect-dos-k8s
ADubhlaoich
left a comment
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.
Generally LGTM but you have updated metadata unnecessarily.
The nd-content-type key and the nd-product value F5DOSN are newer conventions that should be kept: I don't know why they were removed in this PR.
...nt/nap-dos/deployment-guide/installing-nginx-plus-with-dos-and-waf-on-amazon-web-services.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Alan Dooley <a.dooley@f5.com>
…s-and-waf-on-amazon-web-services.md Co-authored-by: Alan Dooley <a.dooley@f5.com>
| toc: true | ||
| # Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this | ||
| nd-content-type: how-to | ||
| nd-product: DOS |
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.
| nd-product: DOS | |
| nd-product: F5DOSN |
| toc: true | ||
| # Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this | ||
| nd-content-type: how-to | ||
| nd-product: DOS |
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.
| nd-product: DOS | |
| nd-product: F5DOSN |
Proposed changes
Add dos k8s and dos k8s with EBPF
Refactor dos documentation
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. ↩