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
bpf, cilium/cmd: remove unused hidden cilium bpf migrate-map
sub-command
#25196
Conversation
It's unused in the datapath since commit bd31f7d ("datapath: Drop nodeport_must_drop_remote constraint"). Signed-off-by: Tobias Klauser <tobias@cilium.io>
…mmand The `cilium bpf migrate-map sub-command` was introduced in 4305f92 ("cilium-migrate-map: port from C to Go") as a temporary CLI wrapper around the logic to migrate bpf maps from bpf/init.sh. Since commit d38dda4 ("init.sh,loader: load overlay programs in Go") that task is performed from within the agent using the same Go code and thus making the migrate-map sub-command obsolete. The sub-command is hidden and was only used in bpf/init.sh, so remove it directly without deprecating it first. Signed-off-by: Tobias Klauser <tobias@cilium.io>
4b2c1f0
to
097e8f0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! 😁 🚀 How did you notice?
Merge conflicts when rebasing one of my WIP branches where I had hacks in |
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
/ci-e2e |
The
cilium bpf migrate-map sub-command
was introduced in 4305f92("cilium-migrate-map: port from from C to Go") as a temporary CLI
wrapper around the logic to migrate bpf maps from
bpf/init.sh
. Sincecommit d38dda4 ("init.sh,loader: load overlay programs in Go") that
task is performed from within the agent using the same Go code and thus
making the migrate-map sub-command obsolete. The sub-command is hidden
and was only used in
bpf/init.sh
, so remove it directly withoutdeprecating it first.