我正在使用azure的容器引擎运行kubernetes集群。我有一个kubernetes服务的问题,那是一个资源监视heapster
。这个吊舱每分钟都会重新启动或类似的东西。我尝试删除heapster部署,replicaset和pod,然后重新创建部署。它立即返回相同的行为。Kubernetes监控服务heapster不断重启
当我看资源与heapster标签,它看起来有点有点怪:
$ kubectl get deploy,rs,po -l k8s-app=heapster --namespace=kube-system
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deploy/heapster 1 1 1 1 17h
NAME DESIRED CURRENT READY AGE
rs/heapster-2708163903 1 1 1 17h
rs/heapster-867061013 0 0 0 17h
NAME READY STATUS RESTARTS AGE
po/heapster-2708163903-vvs1d 2/2 Running 0 0s
出于某种原因,在两个副本集。即使在我删除所有资源并重新部署它们时,名为rs/heapster-867061013
的那个也会重新出现。上面还显示了该容器刚刚开始,这是它不断创建的问题,然后运行几秒钟,然后创建一个新容器。我是运行kubernetes的新手,所以我不确定哪些日志文件与此问题相关。
从heapster容器
heapster.go:72] /heapster source=kubernetes.summary_api:""
heapster.go:73] Heapster version v1.3.0
configs.go:61] Using Kubernetes client with master "https://10.0.0.1:443" and version v1
configs.go:62] Using kubelet port 10255
heapster.go:196] Starting with Metric Sink
heapster.go:106] Starting heapster on port 8082
从heapster保姆容器日志日志
pod_nanny.go:56] Invoked by [/pod_nanny --cpu=80m --extra-cpu=0.5m --memory=140Mi --extra-memory=4Mi --threshold=5 --deployment=heapster --container=heapster --poll-period=300000 --estimator=exponential]
pod_nanny.go:68] Watching namespace: kube-system, pod: heapster-2708163903-mqlsq, container: heapster.
pod_nanny.go:69] cpu: 80m, extra_cpu: 0.5m, memory: 140Mi, extra_memory: 4Mi, storage: MISSING, extra_storage: 0Gi
pod_nanny.go:110] Resources: [{Base:{i:{value:80 scale:-3} d:{Dec:<nil>} s:80m Format:DecimalSI} ExtraPerNode:{i:{value:5 scale:-4} d:{Dec:<nil>} s: Format:DecimalSI} Name:cpu} {Base:{i:{value:146800640 scale:0} d:{Dec:<nil>} s:140Mi Format:BinarySI} ExtraPerNode:{i:{value:4194304 scale:0} d:{Dec:<nil>} s:4Mi Format:BinarySI} Name:memory}]
heapster pod的日志说什么?它是否由于某种错误而退出?另外哪个[restartPolicy](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy)为该窗格设置? – fishi
@fishi我已将日志添加到问题 –
该吊舱已重新启动策略始终 –