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 DNSSelector but it seems from there last comment that this feature is not implemented in Kubernetes.
I explored calico also, but in calico this feature comes under calico-enterprise 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?
Asked
Active
Viewed 340 times
0
Wytrzymały Wiktor
- 11,492
- 5
- 29
- 37
solveit
- 869
- 2
- 12
- 32
-
Hello @solveit. Looks like a feature like this is still not implemented (nor being implemented) in k8s yet. Other sources are pointing towards that Calico solution that you have already mentioned. I am still looking for a possible solution but there is a possibility that it is exactly how you described it. – Wytrzymały Wiktor Jun 29 '21 at 14:35
-
Thanks @WytrzymałyWiktor. How about Kubernetes DNS service https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#introduction to control the egress calls ? With some dns server that I can integrate with k3s and use this service ? – solveit Jun 30 '21 at 06:35
-
Hello @solveit. That would be a topic for a separate question. Remember to follow [these rules](https://stackoverflow.com/help/how-to-ask) if you wish to ask about it. As for your original question, I will post a community wiki answer for it in a moment. – Wytrzymały Wiktor Jul 06 '21 at 08:54
1 Answers
1
This is a community wiki answer. Feel free to expand it.
Unfortunately, the DNSSelector is not yet implemented in Kubernetes (nor being implemented).
Calico Enterprise supports such functionality if you wish to pay for it.
Wytrzymały Wiktor
- 11,492
- 5
- 29
- 37