Merged
Conversation
[ upstream commit 7508733 ] The FromRequires / ToRequires fields were not removed, but instead the length of these fields was restricted to length 0. This allows us to avoid making a breaking change to the format of the resource while still enforcing that users do not use this unsupported field. Fix the upgrade note to conform with this behavior. Fixes: 4fbbc8b ("policy: Reintroduce From/ToRequires but mark them as deprecated") Signed-off-by: Joe Stringer <joe@cilium.io>
[ upstream commit ee738da ] This commit creates some stronger structure around the upgrade notes in the hopes of more clearly communicating to users what is changing and when they may need to take action. The high level categories are: * Action Required * Informational Notes * Changes to Features * Changes to Metrics Furthermore, for feature flags and metrics they are now sorted in the following order: new, changed, deprecated, removed. This commit doesn't modify the text of the release notes, only rearranges the ordering. Signed-off-by: Joe Stringer <joe@cilium.io>
[ upstream commit 5ef8dd6 ] This commit clarifies the action required from users when interacting with network policies during the v1.18 -> v1.19 upgrade. Signed-off-by: Joe Stringer <joe@cilium.io>
[ upstream commit 1914ca9 ] Clarify general wording in the upgrade notes and rearrange some of the items for new features into the relevant docs section. Signed-off-by: Joe Stringer <joe@cilium.io>
[ upstream commit f30efc6 ] Per out-of-band discussion with Robin, update this release note to clarify when there might be packet loss related to the new encryption strict mode feature. Three changes here: - Drops could happen any time the feature is turned on or off - The disruption is only known to occur during the upgrade period - We can simplify the language to address the reader more directly. Signed-off-by: Joe Stringer <joe@cilium.io>
Member
Author
|
/test |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Partial backport of #43913. I dropped the v1.20-specific changes.
Once this PR is merged, a GitHub action will update the labels of these PRs: