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.

Sign up for GitHub

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

Jump to bottom

Implement GC for per-cluster CT/SNAT maps #24576

Merged
merged 2 commits into from
Mar 30, 2023
Merged

Implement GC for per-cluster CT/SNAT maps #24576

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5a9758f
Include clusterID into ctmap.Map
YutaroHayakawa Mar 24, 2023
5562ce2
Implement CT/NAT GC for per-cluster maps
YutaroHayakawa Mar 24, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 4 additions & 0 deletions pkg/maps/ctmap/ctmap.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -213,6 +213,10 @@ type Map struct {
// define maps to the macro used in the datapath portion for the map
// name, for example 'CT_MAP4'.
define string

// This field indicates which cluster this ctmap is. Zero for global
Copy link
Member

Choose a reason for hiding this comment

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

nit: We should probably start revising our usage of "global" to mean "the local cluster", since global sounds confusingly like all clusters. I know the naming is grandfathered in since it was referring to "globally across the node" instead of "per-endpoint CT" so the naming is not super easy here, but there's lots of opportunity to further confuse readers by continuing to use the global phrasing going forward.

// maps and non-zero for per-cluster maps.
clusterID uint32
}

// GCFilter contains the necessary fields to filter the CT maps.
Expand Down