Jackson
Jackson
yes the netctl net inpsect is use the netmaster cache. So maybe u should restart the netmaster.
> not netmaster cache , when server is hang, server is poweroff, netmaster will make many no-released ip. contiv is plugin for docker, product env is not permitted restart docker....
> Also unable to create pods using below the network configuration. > > `{ "Config": { "key": "default:contiv-net", "encap": "vxlan", "gateway": "172.1.16.1", "networkName": "contiv-net", "nwType": "data", "subnet": "172.1.16.0/24", "tenantName": "default",...
@MIBc Is there iptables in the host?
@MIBc Type: NodePort IP: 10.20.175.244 Is the IP is the master's node ip?or is there netplugin run in the 10.20.175.244's host?Not the netmaster. In contiv,Just netplugin support the nodeproxy!
@MIBc Yes, u can see iptables -t nat -nL in node (which run the netplutin not the netmaster ) not the master. Is there some rules about the nodeport?
The pod can access the cluster ip from the pod. Because the netplugin is watching the kubernetes's api-server's services. When u add a services,the netplugin will add a flow in...
May be u can show the flows in the ovs.Such as the picture blow.  
This still exists and is not fixed.