What happened:
Network policy agent today supports only pods that are deployed as a part of deployment/replicaset. If network policies are applied to standalone pods there might be some inconsistencies in the behavior
Format of Pod Name: (pod-template-name)-(random-string)
(pod-template-name): This is the name of the template or controller that creates the Pod. For example, in a Deployment, this would be the name of the Deployment resource. Pods in same deployment will have same pod-template-name
If cx uses standalone pods with same pod-template-name like nginx-a, nginx-b, NP works with them as they belong to same deployment and this will cause inconsistent behavior while applying network policies
What you expected to happen:
Support network policies for standalone pods. Cx should be able to apply policies to individual pods based on pod selectors in a namespace
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
We are working towards providing support for standalone pods
What happened: Network policy agent today supports only pods that are deployed as a part of deployment/replicaset. If network policies are applied to standalone pods there might be some inconsistencies in the behavior
Format of Pod Name: (pod-template-name)-(random-string) (pod-template-name): This is the name of the template or controller that creates the Pod. For example, in a Deployment, this would be the name of the Deployment resource. Pods in same deployment will have same pod-template-name
If cx uses standalone pods with same pod-template-name like nginx-a, nginx-b, NP works with them as they belong to same deployment and this will cause inconsistent behavior while applying network policies
What you expected to happen: Support network policies for standalone pods. Cx should be able to apply policies to individual pods based on pod selectors in a namespace
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?: We are working towards providing support for standalone pods
Environment:
kubectl version):cat /etc/os-release):uname -a):