Skip to content
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

Merged
merged 1 commit into from
Jun 29, 2021

Conversation

jibi
Copy link
Member

@jibi jibi commented Jun 29, 2021

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.

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>
@jibi jibi requested a review from tklauser June 29, 2021 14:24
@jibi jibi requested a review from a team as a code owner June 29, 2021 14:24
@jibi jibi requested a review from qmonnet June 29, 2021 14:24
@maintainer-s-little-helper maintainer-s-little-helper bot added the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jun 29, 2021
@jibi jibi added the release-note/misc This PR makes changes that have no direct user impact. label Jun 29, 2021
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jun 29, 2021
@maintainer-s-little-helper maintainer-s-little-helper bot added this to Needs backport from master in 1.10.2 Jun 29, 2021
Copy link
Member

@qmonnet qmonnet left a 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?

@jibi
Copy link
Member Author

jibi commented Jun 29, 2021

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

@qmonnet
Copy link
Member

qmonnet commented Jun 29, 2021

Will it trigger warnings if the old option name is used?

@jibi
Copy link
Member Author

jibi commented Jun 29, 2021

Will it trigger warnings if the old option name is used?

Yes:

vagrant@k8s1:~$ sudo journalctl -u cilium | grep native
Jun 29 15:19:44 k8s1 cilium-agent[8189]: Flag --native-routing-cidr has been deprecated, This option will be removed in v1.12

@qmonnet
Copy link
Member

qmonnet commented Jun 29, 2021

Discussed offline, and even with the warning it seems OK in the current case. No objection from my side :).

@qmonnet qmonnet added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Jun 29, 2021
@aanm aanm merged commit 4bd2188 into master Jun 29, 2021
@aanm aanm deleted the pr/jibi/deprecate-native-routing-cidr-v1.10 branch June 29, 2021 21:57
@maintainer-s-little-helper maintainer-s-little-helper bot removed this from Needs backport from master in 1.10.2 Jun 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/misc This PR makes changes that have no direct user impact.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants