I think that would be a low priority.
kubespray deployment over 3 nodes for some time today I learned that the cross-service resolution is not working for me because I do not use NodeLocal DNS Cache (doc) which
kubespray employs by default (since kubespray 2.10 release on Oct 16, 2019) which listens over
169.254.25.10 IP by default and cross-service resolution is working as 53/UDP requests are permitted to all addresses within
169.254.0.0/16 range by the
akash-deployment-restrictions Network Policy.
And that is not an issue with the
kubespray deployments suggested by the current Akash documentation but rather with the custom Kubernetes deployments such as mine.
So, I guess the github [netpol] akash-deployment-restrictions prevents PODs from accessing kube-dns over 53/udp, 53/tcp in pod subnet · Issue #1339 · ovrclk/akash · GitHub issue can probably be closed, maybe with some follow-up on:
- Do we really want to allow 53/UDP requests to ALL addresses within
I think we can still leverage
podSelector for letting
NodeLocal DNS Cache service explicitly instead of allowing 53/UDP across
169.254.0.0/16. As well as maybe to support
NodeLocal DNS Cache-less deployments, such as
I’ve been talking with Colin on Monday (July 26th), I’ll create a PR for updating the Akash deployment documentation since it’s missing the
gVisor parts (for which
kubespray actually has a toggle) and few other moments related to its enablement.
I initially disliked the
kubespray, but after been chewing it for awhile, I think it’s good to use it as it is supposed to be used for the Production Ready deployments, it is also getting curated and updated relatively frequently.