Problem statement: Wanted to secure service[actually pod] by limiting access to it by other services/pods inside the same cluster/namespace. I have landed on this below page and tried producing the same in my cluster. It did not work. Even I applied network policy as shown in the example in the below doc, it did not limit access to the new pod which got created without any access label.
A couple of guys from last local KubeMeetup tried it on their cluster and it did not work for them too.
It sounds like a bug in this solution, someone please correct it?