aws / aws/containers-roadmap

[EKS] [EKS windows issue ]: pods created inside the windows node group does not have acess to internet via NAT

Open
#1,344 0 comments 0 reactions 0 assignees View on GitHub
EKS Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

We have created the EKS control plane, after which we have added the self managed node group.
by default the pods are getting the private ip from subnet assigned using cni plugin
but the container running inside pod is not able to ping or access any url in internet.

below are the logs of container
```
>> kubectl logs windows-server-iis-7dcfc7c79b-p876x

Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
True No Success {Common HTTP Features, Default Documen...
Invoke-WebRequest : The remote name could not be resolved:
'dotnetbinaries.blob.core.windows.net'
At line:1 char:32
+ ... Web-Server; Invoke-WebRequest -UseBasicParsing -Uri 'https://dotnetbi ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:Htt
pWebRequest) [Invoke-WebRequest], WebException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShe
ll.Commands.InvokeWebRequestCommand

C:\ServiceMonitor.exe : The term 'C:\ServiceMonitor.exe' is not recognized as
the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:311
+ ... ml>' > C:\inetpub\wwwroot\default.html; C:\ServiceMonitor.exe 'w3svc' ...
+ ~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (C:\ServiceMonitor.exe:String) [
], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

```
any inputs will be appreciated

Contributor guide

Open the contributing guide

Research direction

Start with the reported EKS control plane, self-managed Windows node group, subnet, CNI, and NAT configuration, then reproduce the failure from the pod using the shown kubectl logs and Invoke-WebRequest command. The issue names no repository files or tests; done would require identifying the missing networking or DNS configuration and documenting a verified path for Windows-node pods to reach the internet.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.