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.

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

Remove Listener Creation for Containerd Events #7782

Closed
Nino-K opened this issue Nov 15, 2024 · 0 comments · Fixed by #7781
Closed

Remove Listener Creation for Containerd Events #7782

Nino-K opened this issue Nov 15, 2024 · 0 comments · Fixed by #7781
Assignees
Labels
area/networking area/wsl WSL integration kind/enhancement New feature or request
Milestone

Comments

@Nino-K
Copy link
Member

Nino-K commented Nov 15, 2024

Historically, when containerd events were received, we created listeners to leverage the WSL listener forwarding feature. This was necessary because containerd, unlike Docker, didn't create listeners for running containers. Instead, it routed traffic through iptables rules in the CNI-HOSTPORT-DNAT chain, manipulating container traffic directly.

However, the WSL listener forwarding feature is no longer in use with the new namespaced network configuration. As a result, we no longer need to create listeners for each running container manually, and it should be removed.

@Nino-K Nino-K added kind/enhancement New feature or request area/networking area/wsl WSL integration labels Nov 15, 2024
@Nino-K Nino-K added this to the 1.17 milestone Nov 15, 2024
@Nino-K Nino-K self-assigned this Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/networking area/wsl WSL integration kind/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant