Kubernetes Pod 状态始终处于待定状态

Question

请帮帮我。我正在遵循本指南:https://pleasereleaseme.net/deploy-a-dockerized-asp-net-core-application-to-kubernetes-on-azure-using-a-vsts-ci-cd-pipeline-part-1/ .我的 docker 镜像已成功构建并推送到我的私有(private)容器注册表，我的 CD 管道也没有问题。但是当我尝试使用 kubectl get pods 检查它时，状态总是挂起，当我尝试使用 kubectl describe pod k8s-aspnetcore-deployment-64648bb5ff-fxg2k 时，消息是:

Name:           k8s-aspnetcore-deployment-64648bb5ff-fxg2k
Namespace:      default
Node:           <none>
Labels:         app=k8s-aspnetcore
                pod-template-hash=2020466199
Annotations:    <none>
Status:         Pending
IP:
Controlled By:  ReplicaSet/k8s-aspnetcore-deployment-64648bb5ff
Containers:
  k8s-aspnetcore:
    Image:        mycontainerregistryb007.azurecr.io/k8saspnetcore:2033
    Port:         80/TCP
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-tr892 (ro)
Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  default-token-tr892:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-tr892
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  beta.kubernetes.io/os=windows
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  3m (x57 over 19m)  default-scheduler  0/1 nodes are available: 1 MatchNodeSelector.

这里是 kubectl 描述部署:

Name:                   k8s-aspnetcore-deployment
Namespace:              default
CreationTimestamp:      Sat, 21 Jul 2018 13:41:52 +0000
Labels:                 app=k8s-aspnetcore
Annotations:            deployment.kubernetes.io/revision=2
Selector:               app=k8s-aspnetcore
Replicas:               1 desired | 1 updated | 1 total | 0 available | 1 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        5
RollingUpdateStrategy:  1 max unavailable, 1 max surge
Pod Template:
  Labels:  app=k8s-aspnetcore
  Containers:
   k8s-aspnetcore:
    Image:        mycontainerregistryb007.azurecr.io/k8saspnetcore:2033
    Port:         80/TCP
    Environment:  <none>
    Mounts:       <none>
  Volumes:        <none>
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
OldReplicaSets:  <none>
NewReplicaSet:   k8s-aspnetcore-deployment-64648bb5ff (1/1 replicas created)
Events:
  Type    Reason             Age   From                   Message
  ----    ------             ----  ----                   -------
  Normal  ScalingReplicaSet  26m   deployment-controller  Scaled up replica set k8s-aspnetcore-deployment-7f756cc78c to 1
  Normal  ScalingReplicaSet  26m   deployment-controller  Scaled up replica set k8s-aspnetcore-deployment-64648bb5ff to 1
  Normal  ScalingReplicaSet  26m   deployment-controller  Scaled down replica set k8s-aspnetcore-deployment-7f756cc78c to 0

这里是 kubectl 描述服务:

Name:                     k8s-aspnetcore-service
Namespace:                default
Labels:                   version=test
Annotations:              <none>
Selector:                 app=k8s-aspnetcore
Type:                     LoadBalancer
IP:                       10.0.26.188
LoadBalancer Ingress:     40.112.73.28
Port:                     <unset>  80/TCP
TargetPort:               80/TCP
NodePort:                 <unset>  30282/TCP
Endpoints:                <none>
Session Affinity:         None
External Traffic Policy:  Cluster
Events:
  Type    Reason                Age   From                Message
  ----    ------                ----  ----                -------
  Normal  EnsuringLoadBalancer  26m   service-controller  Ensuring load balancer
  Normal  EnsuredLoadBalancer   25m   service-controller  Ensured load balancer

我不知道我的 Kubernetes 集群设置是否错误，但这是我使用的脚本:

#!/bin/bash

azureSubscriptionId="xxxxxxx-xxxxx-xxxx-xxx-xxxxxxxx"
resourceGroup="k8sResourceGroup"
clusterName="k8sCluster"
location="northeurope"

# Useful if you have more than one Aure subscription
az account set --subscription $azureSubscriptionId

# Resource group for cluster - only availble in certain regions at time of writing
az group create --location $location --name $resourceGroup

# Create actual cluster
az aks create --resource-group $resourceGroup --name $clusterName --node-count 1 --generate-ssh-keys

# Creates a config file at ~/.kube on local machine to tell kubectl which cluster it should work with
az aks get-credentials --resource-group $resourceGroup --name $clusterName

这是我的 deployment.yaml:

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: k8s-aspnetcore-deployment
spec:
  replicas: 1
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 1
  minReadySeconds: 5
  template:
    metadata:
      labels:
        app: k8s-aspnetcore
    spec:
      containers:
      - name: k8s-aspnetcore
        image: mycontainerregistryb007.azurecr.io/k8saspnetcore
        ports:
        - containerPort: 80
      imagePullSecrets:
        - name: k8ssecret
      nodeSelector:
        "beta.kubernetes.io/os": windows

这是我的 service.yaml:

kind: Service
metadata:
  name: k8s-aspnetcore-service
  labels:
    version: test
spec:
  selector:
    app: k8s-aspnetcore
  ports:
  - port: 80
  type: LoadBalancer

Answer 1

describe pod 输出底部的消息中描述了它们处于 Pending 状态的原因:MatchNodeSelector。这意味着 Kubernetes 在您的集群中找不到能够满足 PodSpec 中指定的节点选择标准的节点。

具体来说，很可能是这些行:

nodeSelector:
    "beta.kubernetes.io/os": windows

只有 kubectl describe nodes 会判断是否有可能满足该条件的节点