Add xt_comment and nf_tables kernel modules for k3s support#9
Open
Add xt_comment and nf_tables kernel modules for k3s support#9
Conversation
…upport Enable iptables comment match and nftables in the kernel config, and include the corresponding module packages in all rootfs images. These modules are required by Kubernetes kube-proxy (iptables mode) and modern iptables-nft backend. Without xt_comment, kube-proxy cannot create ClusterIP routing rules, breaking all pod networking.
kvinwang
force-pushed
the
add-k3s-kernel-modules
branch
from
73defa8 to
50172d8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
nf_tablesand sub-modules in kernel config (dstack-docker.cfg)xt_commentand 12nft_*module packages in all rootfs imagesxt_multiport,xt_statistic,xt_redirect,xt_tcpmss,xt_ct,xt_log,xt_limitfor broader Kubernetes networking compatibilityWhy
Running k3s inside a dstack CVM fails because:
xt_comment.kowas compiled (CONFIG_NETFILTER_XT_MATCH_COMMENT=m) but not included in rootfsnf_tableswas completely disabledWithout
xt_comment, kube-proxy cannot create iptables rules with comment matches, breaking all ClusterIP service routing. This affects any Kubernetes distribution (k3s, k0s, kubeadm).Mirror of Dstack-TEE/meta-dstack PRs #42 and #43.