Question

对于每个https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html，我运行命令eksctl utils install-vpc-controllers --cluster --approve

我的EKS版本是v1.16.3。我尝试将Windows docker映像部署到Windows节点。我在下面出现错误。

警告FailedCreatePodSandBox 31s kubelet，ip-west-2.compute.internal创建Pod沙箱失败：rpc错误：代码=未知desc =无法为Pod“ mrestapi-67fb477548-v4njs”设置沙箱容器“ ab8001f7b01f5c154867b7e”网络： networkPlugin CNI无法设置Pod“ mrestapi-67fb477548-v4njs_ui”网络：无法解析Kubernetes args：Pod没有标签vpc.amazonaws.com/PrivateIPv4Address

$ kubectl logs vpc-resource-controller-645d6696bc-s5rhk -n kube-system
I1010 03:40:29.041761       1 leaderelection.go:185] attempting to acquire leader lease  kube-system/vpc-resource-controller...
I1010 03:40:46.453557       1 leaderelection.go:194] successfully acquired lease kube-system/vpc-resource-controller
W1010 23:57:53.972158       1 reflector.go:341] pkg/mod/k8s.io/client-go@v0.0.0-20180910083459-2cefa64ff137/tools/cache/reflector.go:99: watch of *v1.Pod ended with: too old resource version: 1480444 (1515040)

它抱怨资源版本太旧。如何升级版本？

Answer 1

要解决此问题，我会...

首先列出组件以确保它们正在运行：

$kubectl get pod -n kube-system | grep vpc
vpc-admission-webhook-deployment-7f67d7b49-wgzbg   1/1     Running   0          38h
vpc-resource-controller-595bfc9d98-4mb2g           1/1     Running   0          29

如果他们正在运行，请检查其日志

kubectl logs <vpc-yadayada> -n kube-system

请确保您使用的实例类型每个ENI都具有enough available IPs，因为在Windows世界中，仅使用一个ENI，并且限制为每个ENI的最大可用IP减去主要IP地址的一个。在超出ENI可用IP的数量之前，我就遇到了此错误。
确认您的广告连播选择器正确

nodeSelector:
  kubernetes.io/os: windows
  kubernetes.io/arch: amd64

作为一个轶事，到目前为止，我已经完成了您在几个群集上链接的文档的To enable Windows support for your cluster with a macOS or Linux client部分下提到的步骤，并且它们运行良好。

Answer 2

您的输出是什么

kubectl describe node <windows_node>

？

如果是这样的话：

  vpc.amazonaws.com/CIDRBlock:           0
  vpc.amazonaws.com/ENI:                 0
  vpc.amazonaws.com/PrivateIPv4Address:  0

然后您需要重新创建具有不同实例类型的节点组...

然后尝试部署它：

apiVersion: apps/v1
kind: Deployment
metadata:
  name: windows-server-iis-test
  namespace: default
spec:
  selector:
    matchLabels:
      app: windows-server-iis-test
      tier: backend
      track: stable
  replicas: 1
  template:
    metadata:
      labels:
        app: windows-server-iis-test
        tier: backend
        track: stable
    spec:
      containers:
      - name: windows-server-iis-test
        image: mcr.microsoft.com/windows/servercore:1809
        ports:
        - name: http
          containerPort: 80
        imagePullPolicy: IfNotPresent
        command:
        - powershell.exe
        - -command
        - "Add-WindowsFeature Web-Server; Invoke-WebRequest -UseBasicParsing -Uri 'https://dotnetbinaries.blob.core.windows.net/servicemonitor/2.0.1.6/ServiceMonitor.exe' -OutFile 'C:\\ServiceMonitor.exe'; echo '<html><body><br/><br/><marquee><H1>Hello EKS!!!<H1><marquee></body><html>' > C:\\inetpub\\wwwroot\\default.html; C:\\ServiceMonitor.exe 'w3svc'; "
        resources:
          limits:
            cpu: 256m
            memory: 256Mi
          requests:
            cpu: 128m
            memory: 100Mi
      nodeSelector:
        kubernetes.io/os: windows
---
apiVersion: v1
kind: Service
metadata:
  name: windows-server-iis-test
  namespace: default
spec:
  ports:
  - port: 80
    protocol: TCP
    targetPort: 80
  selector:
    app: windows-server-iis-test
    tier: backend
    track: stable
  sessionAffinity: None
  type: ClusterIP

kubectl proxy

打开浏览器http：// localhost：8001 / api / v1 / namespaces / default / services / http：windows-server-iis-test：80 / proxy / default.html将显示带有Hello EKS文字的网页

Answer 3

我删除了Windows节点，重新创建了具有不同实例类型的Windows节点。但是，它没有用。
已删除的Windows节点组，已重新创建的Windows节点组。它没有用。
最后，我删除了整个EKS集群，重新创建了eks集群。命令kubectl describe node 给我下面的输出。

  vpc.amazonaws.com/CIDRBlock           0         0
  vpc.amazonaws.com/ENI                 0         0
  vpc.amazonaws.com/PrivateIPv4Address  1         1

部署了Windows-server-iis.yaml。它按预期工作。问题的根本原因是谜。

EKS，Windows节点。 networkPlugin cni失败

3 个答案: