Kubernetes 部署挂起

Question

遵循文档中的部署示例。我正在尝试部署示例 nginx。使用以下配置：

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: nginx-deployment
spec:
  replicas: 3
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:1.7.9
        ports:
        - containerPort: 80

到目前为止，部署总是挂起。我试图查看是否出于任何原因需要部署一个名为 nginx 的 pod。那并没有解决问题。

$ sudo kubectl get deployments
NAME               UPDATEDREPLICAS   AGE
nginx-deployment   0/3               34m

$ sudo kubectl describe deployments
Name:                           nginx-deployment
Namespace:                      default
CreationTimestamp:              Sat, 30 Jan 2016 06:03:47 +0000
Labels:                         app=nginx
Selector:                       app=nginx
Replicas:                       0 updated / 3 total
StrategyType:                   RollingUpdate
RollingUpdateStrategy:          1 max unavailable, 1 max surge, 0 min ready    seconds
OldReplicationControllers:      nginx (2/2 replicas created)
NewReplicationController:       <none>
No events.

当我检查来自 kubernetes 的事件时，我看不到属于此部署的事件。有谁之前经历过这个吗？

版本如下：

Client Version: version.Info{Major:"1", Minor:"1", GitVersion:"v1.1.3", GitCommit:"6a81b50c7e97bbe0ade075de55ab4fa34f049dc2", GitTreeState:"clean"}
Server Version: version.Info{Major:"1", Minor:"1", GitVersion:"v1.1.3", GitCommit:"6a81b50c7e97bbe0ade075de55ab4fa34f049dc2", GitTreeState:"clean"}

Answer 1

如果部署没有创建任何 pod，您可以查看事件，例如可能会报告错误：

kubectl get events --all-namespaces                         
NAMESPACE   LASTSEEN   FIRSTSEEN   COUNT     NAME                   KIND         SUBOBJECT   TYPE      REASON         SOURCE                    MESSAGE
default     8m         2d          415       wordpress              Ingress                  Normal    Service        loadbalancer-controller   no user specified default backend, using system default
kube-lego   2m         8h          49        kube-lego-7c66c7fddf   ReplicaSet               Warning   FailedCreate   replicaset-controller     Error creating: pods "kube-lego-7c66c7fddf-" is forbidden: service account kube-lego/kube-lego2-kube-lego was not found, retry after the service account is created

也看看kubectl get rs --all-namespaces。

Answer 2

我从问题页面找到了答案

为了在启用并重新启动 kube-apiserver 后使部署正常工作，您还必须重新启动 kube-controller-manager。