-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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: deprecate native-routing-cidr from v1.10 #16688
Conversation
Given that the change to deprecate the native-routing-cidr option in favor of ipv4-native-routing-cidr was supposed to be backported to v1.10, update the docs to move the deprecation notice under the v1.10 section. Signed-off-by: Gilberto Bertin <gilberto@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.
Change looks good, but is it OK to deprecate an option retrospectively after a major version has been released?
I'd say it's OK as this change is not going to break any existing setup |
Will it trigger warnings if the old option name is used? |
Yes:
|
Discussed offline, and even with the warning it seems OK in the current case. No objection from my side :). |
Given that the change to deprecate the native-routing-cidr option in
favor of ipv4-native-routing-cidr was supposed to be backported to
v1.10, update the docs to move the deprecation notice under the v1.10
section.