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: mark node-to-node IPSec encryption as beta #16200
Conversation
Mark node-to-node encryption explicitly as a beta feature, to indicate that some issues might remain to be fixed. Signed-off-by: Quentin Monnet <quentin@isovalent.com>
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.
Looks about right to me, did you also get an ack from @jrfastab ? Might be worth pinging him before we merge this.
I'm OK with this, but would consider adding workflows for node to node case and then flipping it out of beta. But, without workflows for us to verify its working in all our supported environments its easy to have a regression in one of the corner cases. So, marking BETA makes some sense until this happens. |
Let's backport anyway because otherwise in v1.9 it's not super clear that node-to-node encryption is beta. |
Keep node-to-node encryption in beta mode, to indicate that some issues might remain to be fixed.
(Note: The whole IPsec page was marked as
stable/beta
for 1.9).