<p>I am trying to implement Kubernetes Network policy in my application on the basis of domain name to control the Egress and Ingress calls to the pod. I found <a href="https://github.com/kubernetes/kubernetes/issues/50453" rel="nofollow noreferrer">DNSSelector</a> but it seems from there <a href="https://github.com/kubernetes/kubernetes/issues/50453#issuecomment-368334028" rel="nofollow noreferrer">last comment</a> that this feature is not implemented in Kubernetes. <br/>I explored calico also, but in calico this feature comes under <a href="https://docs.projectcalico.org/security/calico-enterprise/egress-access-controls" rel="nofollow noreferrer">calico-enterprise</a> hence it is paid. Can someone let me know if any other way out there to achieve this or maybe DNSSelector is being implemented now in Kubernetes?</p>

solveit
<p>This is a community wiki answer. Feel free to expand it.</p>
<p>Unfortunately, the <a href="https://github.com/kubernetes/kubernetes/issues/50453" rel="nofollow noreferrer">DNSSelector</a> is not yet implemented in Kubernetes (nor being implemented).</p>
<p><a href="https://docs.projectcalico.org/security/calico-enterprise/egress-access-controls" rel="nofollow noreferrer">Calico Enterprise</a> supports such functionality if you wish to pay for it.</p>
