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

Review Cilium datapath compatibility with upstream Kubernetes iptables management changes #27548

Closed
joestringer opened this issue Aug 16, 2023 · 3 comments
Closed

Review Cilium datapath compatibility with upstream Kubernetes iptables management changes #27548

joestringer opened this issue Aug 16, 2023 · 3 comments
Labels
sig/datapath Impacts bpf/ or low-level forwarding details, including map management and monitor messages. stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.

Comments

@joestringer
Copy link
Member

The following KEP in k8s will change the way that upstream iptables rules are configured:

kubernetes/enhancements#3178

We should review the way these changes will impact Cilium.
@joestringer joestringer added the sig/datapath Impacts bpf/ or low-level forwarding details, including map management and monitor messages. label Aug 16, 2023
@aojea
Copy link
Contributor

aojea commented Aug 16, 2023 •
edited

Cilium has to use the chain KUBE-IPTABLES-HINT, that was added for this purpose https://github.com/kubernetes/kubernetes/blob/b1e35d5616e066c4b0b3f550c33bbf67bb3f876e/pkg/kubelet/kubelet_network_linux.go#L34 and is installed and renewed by kubelet

https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/3178-iptables-cleanup#pre-alpha

@github-actions
Copy link

This issue has been automatically marked as stale because it has not
had recent activity. It will be closed if no further activity occurs.

@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 Oct 16, 2023
@github-actions
Copy link

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

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
sig/datapath Impacts bpf/ or low-level forwarding details, including map management and monitor messages. stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@joestringer @aojea