Re: [kubernetes-users] howto define isolated vlan definitions

> if they were running on the same node, their src ip will be the nodes ip Are you tring nodeport service? You can try to configure externalTrafficPolicy = Local, then it will perserve the source pod IP. 2018-01-30 16:00 GMT+08:00 Oğuz Yarımtepe : > I had tested

Re: [kubernetes-users] howto define isolated vlan definitions

I had tested NetworkPolicy issue. The problem is, even the pods are isolated, if they were running on the same node, their src ip will be the nodes ip. Isolating the worker nodes and defining vlans for each of them and defining pods according to these tags is a solution but, my vlan number is more

Re: [kubernetes-users] howto define isolated vlan definitions

Look into NetworkPolicy - it's not your traditional VLAN approach to ACL, it's more dynamic and application-focused. On Mon, Jan 29, 2018 at 10:27 PM, Oğuz Yarımtepe wrote: > My current k8s structure is 2 worker and one master node deployment. I am > testing it with

[kubernetes-users] howto define isolated vlan definitions

My current k8s structure is 2 worker and one master node deployment. I am testing it with NodePort services. Now we will install a bigger cluster, 3 master and more worker nodes. The problem is, using NodePort is causing all the services exit with the same worker node ips. But we need vlan