遵循文档中的部署示例。我正在尝试部署示例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的吊舱。但这并没有解决问题。
$ 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"}发布于 2016-02-12 16:22:54
我从问题页那里找到了答案
为了使部署在启用后工作并重新启动kube,还必须重新启动kube-控制器-管理器。
发布于 2018-05-16 21:16:07
如果部署没有创建任何吊舱,您可以查看事件,可能会在那里报告错误,例如:
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。
发布于 2016-01-31 00:01:03
您可以检查命令kubectl describe pod name_of_your_pod的错误所在。
https://stackoverflow.com/questions/35098931
复制相似问题