fix(provider): kube-dns network policy selectors

[arno01]

Tested on my v0.14.1-rc6 provider.
I am gonna prepare a patch for 0.14.1-rc6 as well.

Tested with

$ cat dnsutils.yaml 
---
version: "2.0"

services:
  dnsutils:
    image: gcr.io/kubernetes-e2e-test-images/dnsutils:1.3
    command:
      - "sh"
      - "-c"
    args:
      - sleep 1d
    expose:
      - port: 8080
        as: 80
        to:
          - global: true

profiles:
  compute:
    dnsutils:
      resources:
        cpu:
          units: 1.0
        memory:
          size: 128Mi 
        storage:
          size: 128Mi
  placement:
    akash:
      signedBy:
        anyOf:
          - "akash1365yvmc4s7awdyj3n2sav7xfx76adc6dnmlx63"
      pricing:
        dnsutils:
          denom: uakt
          amount: 100

deployment:
  dnsutils:
    akash:
      profile: dnsutils
      count: 1

DNS over TCP

nslookup -vc

/ # nslookup -vc kubernetes.default.svc.cluster.local
Server:		10.233.0.10
Address:	10.233.0.10#53

Name:	kubernetes.default.svc.cluster.local
Address: 10.233.0.1

dig +tcp

/ # dig +noall +answer +tcp kubernetes.default.svc.cluster.local
kubernetes.default.svc.cluster.local. 21 IN A	10.233.0.1

To confirm the DNS packets are the TCP ones:

k8s-master# nsenter -n -t $(pidof -s coredns) tcpdump -qenn port 53

DNS over UDP

same as DNS over TCP but without -vc nslookup flag nor +tcp dig flag.

[arno01]

cc @hydrogen18 @boz @dmikey

[arno01]

Can't seem to create a PR against the v0.14.1-rc6 tag, so here is the comparison https://github.com/ovrclk/akash/compare/v0.14.1-rc6...arno01:tag-v0.14.1-rc6-kube-dns-fix?expand=1

commit arno01@5c81676

[boz]

Thanks @arno01! 0.14.x tags are cut from the mainnet/main branch - can you make a PR against that too?

[arno01]

Thanks @arno01! 0.14.x tags are cut from the mainnet/main branch - can you make a PR against that too?

Yep!
#1441