Skip to content

nodemap: remove v1 map #38251

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

Merged
merged 1 commit into from
May 28, 2025
Merged

Conversation

julianwiedmann
Copy link
Member

#31431 introduced v2 of the nodemap, and as of v1.16 the datapath only uses this v2 map. Hence it's safe to remove the agent logic that was still populating the v1 map.

Fixes: #34670

@julianwiedmann julianwiedmann added area/datapath Impacts bpf/ or low-level forwarding details, including map management and monitor messages. release-note/misc This PR makes changes that have no direct user impact. kind/tech-debt Technical debt labels Mar 18, 2025
@julianwiedmann
Copy link
Member Author

/test

@julianwiedmann julianwiedmann requested a review from ldelossa March 18, 2025 10:07
@julianwiedmann julianwiedmann marked this pull request as ready for review March 18, 2025 10:07
@julianwiedmann julianwiedmann requested review from a team as code owners March 18, 2025 10:07
@julianwiedmann julianwiedmann requested a review from asauber March 18, 2025 10:07
Copy link
Member

@asauber asauber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cilium-dbg changes look good

Copy link
Contributor

@ldelossa ldelossa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall looks good to me, just a comment on where v1 map deletion should occur.

@julianwiedmann
Copy link
Member Author

/test

Copy link

This pull request has been automatically marked as stale because it
has not had recent activity. It will be closed if no further activity
occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale. label Apr 26, 2025
Copy link

This pull request has not seen any activity since it was marked stale.
Closing.

@github-actions github-actions bot closed this May 10, 2025
auto-merge was automatically disabled May 10, 2025 02:05

Pull request was closed

@julianwiedmann julianwiedmann force-pushed the 1.18-node-map branch 3 times, most recently from 7f72769 to 9b16620 Compare May 28, 2025 11:39
cilium#31431 introduced v2 of the nodemap,
and as of v1.16 the datapath only uses this v2 map. Hence it's safe to
remove the agent logic that was still populating the v1 map.

Fixes: cilium#34670
Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
@julianwiedmann
Copy link
Member Author

/test

@maintainer-s-little-helper maintainer-s-little-helper bot added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label May 28, 2025
@julianwiedmann julianwiedmann added this pull request to the merge queue May 28, 2025
Merged via the queue into cilium:main with commit 24e2387 May 28, 2025
67 of 68 checks passed
@julianwiedmann julianwiedmann deleted the 1.18-node-map branch May 28, 2025 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/datapath Impacts bpf/ or low-level forwarding details, including map management and monitor messages. kind/tech-debt Technical debt 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. stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ipsec: phase out NodeMap version 1 for v1.17.0
3 participants