Add security recommendations documentation #1702
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
vepatel
approved these changes
Jun 28, 2021
pleshakov
reviewed
Jun 30, 2021
There was a problem hiding this comment.
Hi @soneillf5
Could you update https://raw.githubusercontent.com/nginxinc/kubernetes-ingress/master/docs-web/configuration/index.rst so that the document is visible via TOC -- https://deploy-preview-1702--nginx-kubernetes-ingress.netlify.app/nginx-ingress-controller/configuration/security/ ?
done. |
JTorreG
reviewed
Jul 5, 2021
pleshakov
approved these changes
Jul 6, 2021
brianehlert
approved these changes
Jul 6, 2021
ciarams87
approved these changes
Jul 7, 2021
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 change introduces a new section into docs-web/configuration for security best practices.
It should highlight risks, mitigations and best practices that a user should be aware of and responsible for.
Checklist
Before creating a PR, run through this checklist and mark each as complete.