Prepare for release v1.10.9 #19224
Merged
Prepare for release v1.10.9 #19224
Conversation
This file contains 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
aanm
added
backport/1.10
kind/release
maintainer-s-little-helper
bot
added
the
kind/backports
aanm
requested review from
a team and
joestringer
and removed request for
a team
joestringer
reviewed
Mar 27, 2022
CHANGELOG.md
Outdated
| * Fix issue where StatefulSet pod restarts could trigger persistent connectivity issues for the pods due to overzealous CiliumEndpoint resource removal by cilium-agent instances (Backport PR #19127, Upstream PR #18864, @timoreimann) | ||
| * hubble: Added nil check in filterByTCPFlags() to avoid segfault (Backport PR #19023, Upstream PR #18877, @wazir-ahmed) | ||
| * ipam/crd: Fix spurious "Unable to update CiliumNode custom resource" failures in cilium-agent (Backport PR #19062, Upstream PR #17856, @gandro) | ||
| * Prevent unmanaged pods in GKE's containerd flavors. *Important:* Users should update their node taints from `node.cilium.io/agent-not-ready=true:NoSchedule` to `node.cilium.io/agent-not-ready=true:NoExecute`. *Important:* During the first node reboot after the fix is applied pods may still get IPs from the default CNI as cilium-node-init is only run later in the node startup process. The fix will then be in place for all subsequent reboots. (Backport PR #18835, Upstream PR #18486, @bmcustodio) |
There was a problem hiding this comment.
It'd be nice to highlight this a bit more when it comes to the release summary, this is a change for not only GKE users. Bruno was working on a PR to clarify impact & necessary action required from users this in the docs, #19186 . I don't think we made this clear enough when we backported this to 1.11 and did the release.
nbusseneau
approved these changes
Mar 28, 2022
qmonnet
approved these changes
Mar 28, 2022
Signed-off-by: André Martins <andre@cilium.io>
aanm
force-pushed
the
pr/prepare-v1.10.9
branch
from
390d9e2
to
af29006
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary of Changes
Minor Changes:
Bugfixes:
Important: Users should update their node taints from
node.cilium.io/agent-not-ready=true:NoScheduletonode.cilium.io/agent-not-ready=true:NoExecute.Important: During the first node reboot after the fix is applied pods may still get IPs from the default CNI as cilium-node-init is only run later in the node startup process. The fix will then be in place for all subsequent reboots. (Backport PR v1.10 backports 2022-02-17 #18835, Upstream PR Prevent unmanaged pods in GKE's containerd flavors #18486, @bmcustodio)
CI Changes:
Misc Changes:
Other Changes: