aws/amazon-vpc-cni-k8s

dnsConfig are ignored for Windows pods

Closed this issue · 4 comments

orest-gulman commented

I'm running EKS K8S 1.30 with EC2 Windows workers nodes only, coredns runing on fargate
There is an issue with dnsConfig that are ignored for Windows pods:

    spec:
      dnsPolicy: "None"
      dnsConfig:
        nameservers:
          - 192.168.1.100
        searches:
          - custom.domain

C:\app>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : eks-app
   Primary Dns Suffix  . . . . . . . : custom.domain
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : custom.namespace.svc.cluster.local
                                       svc.cluster.local
                                       cluster.local

Ethernet adapter vEthernet (cid-54890e7f-6a27-434b-ab4c-12ba9c74c1e6):

   Connection-specific DNS Suffix  . : custom.namespace.svc.cluster.locall
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Container Adapter
   Physical Address. . . . . . . . . : 00-15-5D-21-52-E4
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::e67b:4cd8:d426:be86%18(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.50.130.207(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.50.130.1
   DNS Servers . . . . . . . . . . . : 172.20.0.10
   NetBIOS over Tcpip. . . . . . . . : Disabled
   Connection-specific DNS Suffix Search List :
                                       custom.namespace.svc.cluster.local
                                       svc.cluster.local
                                       cluster.local

Expected to happen:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : eks-app
   Primary Dns Suffix  . . . . . . . : custom.domain
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : custom.domain

Ethernet adapter vEthernet (cid-54890e7f-6a27-434b-ab4c-12ba9c74c1e6):

   Connection-specific DNS Suffix  . : custom.domain
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Container Adapter
   Physical Address. . . . . . . . . : 00-15-5D-21-52-E4
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::e67b:4cd8:d426:be86%18(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.50.130.207(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.50.130.1
   DNS Servers . . . . . . . . . . . : 172.20.0.10
   NetBIOS over Tcpip. . . . . . . . : Disabled
   Connection-specific DNS Suffix Search List :
                                       custom.domain
orsenthil commented

VPC CNI is a Linux only CNI. The windows CNI allocation is managed by this project - https://github.com/aws/amazon-vpc-cni-plugins Please raise the ticket there.

github-actions commented

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.

achevuru commented

@orest-gulman To add, CNI plugin is in no way involved with configuring DNS settings for a Pod. Please check your kubelet config or see if there was an issue with dnsConfig section of your pod.

orest-gulman commented

@orest-gulman To add, CNI plugin is in no way involved with configuring DNS settings for a Pod. Please check your kubelet config or see if there was an issue with dnsConfig section of your pod.

Understood. Same manifest.yml works well on onprem k8s with calico cni, but on EKS does't. Thanks anyway