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
daemon: fix issue where IPAM options in custom CNI confs was ignored #26732
Merged
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
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
Jul 10, 2023
squeed
added
the
release-note/misc
This PR makes changes that have no direct user impact.
label
Jul 10, 2023
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
Jul 10, 2023
tentatively setting this as release-note misc, since we will (hopefully) ship no releases with this label! |
squeed
added
the
needs-backport/1.14
This PR / issue needs backporting to the v1.14 branch
label
Jul 10, 2023
joamaki
approved these changes
Jul 10, 2023
gentoo-root
reviewed
Jul 10, 2023
As part of a CNI refactor, a bug was introduced where node-specific IPAM overrides were no longer being loaded. Specifically, the parsed network configuration wasn't properly being passed down to the NodeDiscovery manager. Fixes: cilium#26731 Fixes: 1254bf4 Signed-off-by: Casey Callendrello <cdc@isovalent.com>
squeed
force-pushed
the
fix-cni-ipam-conf
branch
from
July 10, 2023 12:05
7cea69f
to
5217391
Compare
Thanks for the review; fixed. |
gentoo-root
approved these changes
Jul 10, 2023
/test |
All green, merging |
christarazi
added
area/daemon
Impacts operation of the Cilium daemon.
area/cni
Impacts the Container Networking Interface between Cilium and the orchestrator.
labels
Jul 12, 2023
jibi
added
backport-pending/1.14
The backport for Cilium 1.14.x for this PR is in progress.
and removed
needs-backport/1.14
This PR / issue needs backporting to the v1.14 branch
labels
Jul 13, 2023
maintainer-s-little-helper
bot
moved this from Needs backport from main
to Backport pending to v1.14
in 1.14.0
Jul 13, 2023
aanm
added
backport-done/1.14
The backport for Cilium 1.14.x for this PR is done.
and removed
backport-pending/1.14
The backport for Cilium 1.14.x for this PR is in progress.
labels
Jul 14, 2023
maintainer-s-little-helper
bot
moved this from Backport pending to v1.14
to Backport done to v1.14
in 1.14.0
Jul 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/cni
Impacts the Container Networking Interface between Cilium and the orchestrator.
area/daemon
Impacts operation of the Cilium daemon.
backport-done/1.14
The backport for Cilium 1.14.x for this PR is done.
kind/bug
This is a bug in the Cilium logic.
release-note/misc
This PR makes changes that have no direct user impact.
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.
As part of a CNI refactor, a bug was introduced where node-specific IPAM overrides were no longer being loaded. Specifically, the parsed network configuration wasn't properly being passed down to the NodeDiscovery manager.
Fixes: #26731
Fixes: 1254bf4