You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When edgemesh-agent is running on the centos8 system, we cannot see the EDGE-MESH chain through the command:
iptables -t nat -nvL | grep EDGE-MESH
However, we can see the EDGE-MESH chain on the ubuntu 18.04 system.
PS:
what kind iptables centos8 use: iptables v1.8.2 (nf_tables)
what kind iptables ubuntu18.04 use: iptables v1.6.1 (legacy)
What you expected to happen:
No matter which system the edgemesh-agent is running on, you can use the iptables command to see the EDGE-MESH chain on the host.
Anything else we need to know?:
I found that there are two types of iptables: iptables-legacy and iptables-nft. The iptables chain and rules cannot be shared between the two, so the chain and rules created with iptables(legacy) cannot be seen in iptables(nf_tables).
Kube-Proxy also had the same problem, and k8s officially gave a repair plan, you can refer to: kubernetes/kubernetes#82966
Environment:
EdgeMesh version: v1.7.1
Kubernetes version (use kubectl version): v1.18.2
KubeEdge version(e.g. cloudcore --version and edgecore --version): v1.7.1
The text was updated successfully, but these errors were encountered:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
What happened:
When edgemesh-agent is running on the centos8 system, we cannot see the EDGE-MESH chain through the command:
However, we can see the EDGE-MESH chain on the ubuntu 18.04 system.
PS:
what kind iptables centos8 use: iptables v1.8.2 (nf_tables)
what kind iptables ubuntu18.04 use: iptables v1.6.1 (legacy)
What you expected to happen:
No matter which system the edgemesh-agent is running on, you can use the
iptables
command to see the EDGE-MESH chain on the host.Anything else we need to know?:
I found that there are two types of iptables:
iptables-legacy
andiptables-nft
. The iptables chain and rules cannot be shared between the two, so the chain and rules created with iptables(legacy) cannot be seen in iptables(nf_tables).Kube-Proxy also had the same problem, and k8s officially gave a repair plan, you can refer to: kubernetes/kubernetes#82966
Environment:
kubectl version
): v1.18.2cloudcore --version
andedgecore --version
): v1.7.1The text was updated successfully, but these errors were encountered: