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.
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.
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>
Co-authored-by: Alan Dooley <a.dooley@f5.com>
Co-authored-by: Alan Dooley <a.dooley@f5.com>
…d-mitigation..md Co-authored-by: Daniel Edgar <d.edgar@f5.com>
…into app-protect-dos-k8s
|
This PR is stale because it has been open 90 days with no activity. Remove the stale label or add a comment to keep it open. If you do not take action, this will be closed in 10 days. |
|
This PR is stale and slated to be closed. If it needs to be revived, let me know. |
|
Closing. Can reopen if needed. Reopening will require a content plan. |
|
🎉 Thank you for your contribution! It appears you have not yet signed the F5 Contributor License Agreement (CLA), which is required for your changes to be incorporated into an F5 Open Source Software (OSS) project. Please kindly read the F5 CLA and reply on a new comment with the following text to agree: I have hereby read the F5 CLA and agree to its terms 1 out of 2 committers have signed the CLA. |
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. ↩