-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
docs/encryption: Document limitations and workarounds #15876
docs/encryption: Document limitations and workarounds #15876
Conversation
4c6d0da
to
be3884a
Compare
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.
I wonder if the limitation should have a subsection title or paragraph name, or whatever could “summarise” the issue briefly at the top. My concern is that users need to read through ~10 lines of text to understand what the limitation is and if they are concerned at all.
Looks good otherwise.
This adds a section in to the transparent encryption getting started guide explaining that due to potential delays in IPCache updates, it is possible for both IPsec and Wireguard to send out packets unencrypted. Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
be3884a
to
5574251
Compare
Thanks! I decided to add a subtitle called |
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.
Subtitle tells it well and looks good to me, thank you for the change!
This adds a section in to the transparent encryption getting started
guide explaining that due to potential delays in IPCache updates, it is
possible for both IPsec and Wireguard to send out packets unencrypted.