Kubernetes 库伯内特斯不断地杀死和重建最后一个豆荚
kubernetes正在不断删除并重新创建最后一个(第三个)容器。它从运行状态变为终止状态。Kubernetes UI的状态显示为:'终止:ExitCode:${state.Terminated.ExitCode}' 我的部署YAML:Kubernetes 库伯内特斯不断地杀死和重建最后一个豆荚,kubernetes,gcp,Kubernetes,Gcp,kubernetes正在不断删除并重新创建最后一个(第三个)容器。它从运行状态变为终止状态。Kubernetes UI的状态显示为:'终止:ExitCode:${state.Terminated.ExitCode}' 我的部署YAML: apiVersion: autoscaling/v1 kind: HorizontalPodAutoscaler metadata: name: openapi spec: scaleTargetRef: kind: Deployment
apiVersion: autoscaling/v1
kind: HorizontalPodAutoscaler
metadata:
name: openapi
spec:
scaleTargetRef:
kind: Deployment
name: openapi
minReplicas: 3
maxReplicas: 10
targetCPUUtilizationPercentage: 75
---
kind: Service
apiVersion: v1
metadata:
name: openapi
spec:
selector:
app: openapi
ports:
- name: http
protocol: TCP
port: 80
targetPort: 8080
- name: https
protocol: TCP
port: 443
targetPort: 8443
type: LoadBalancer
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: openapi
spec:
template:
metadata:
labels:
app: openapi
spec:
containers:
- name: openapi
image: us.gcr.io/PROJECT_ID/openapi:latest
imagePullPolicy: Always
ports:
- containerPort: 8080
kubectl get events-n命名空间的部分输出
:
Pod Normal Created kubelet Created container
Pod Normal Started kubelet Started container
Pod Normal Killing kubelet Killing container with id docker://openapi:Need to kill Pod
ReplicaSet Normal SuccessfulCreate replicaset-controller (combined from similar events): Created pod: openapi-7db5f8d479-p7mcl
ReplicaSet Normal SuccessfulDelete replicaset-controller (combined from similar events): Deleted pod: openapi-7db5f8d479-pgmxf
HorizontalPodAutoscaler Normal SuccessfulRescale horizontal-pod-autoscaler New size: 2; reason: Current number of replicas above Spec.MaxReplicas
HorizontalPodAutoscaler Normal SuccessfulRescale horizontal-pod-autoscaler New size: 3; reason: Current number of replicas below Spec.MinReplicas
Deployment Normal ScalingReplicaSet deployment-controller Scaled up replica set openapi-7db5f8d479 to 3
Deployment Normal ScalingReplicaSet deployment-controller Scaled down replica set openapi-7db5f8d479 to 2
kubectl描述pod-n默认openapi-7db5f8d479-2d2nm
用于产卵并被杀死的pod:
每次一个豆荚被库伯内特斯杀死后,都会产生一个具有不同唯一id的不同豆荚
Name: openapi-7db5f8d479-2d2nm
Namespace: default
Node: gke-testproject-default-pool-28ce3836-t4hp/10.150.0.2
Start Time: Thu, 23 Nov 2017 11:50:17 +0000
Labels: app=openapi
pod-template-hash=3861948035
Annotations: kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicaSet","namespace":"default","name":"openapi-7db5f8d479","uid":"b7b3e48f-ceb2-11e7-afe7-42010a960003"...
kubernetes.io/limit-ranger=LimitRanger plugin set: cpu request for container openapi
Status: Terminating (expires Thu, 23 Nov 2017 11:51:04 +0000)
Termination Grace Period: 30s
IP:
Created By: ReplicaSet/openapi-7db5f8d479
Controlled By: ReplicaSet/openapi-7db5f8d479
Containers:
openapi:
Container ID: docker://93d2f1372a7ad004aaeb34b0bc9ee375b6ed48609f505b52495067dd0dcbb233
Image: us.gcr.io/testproject-175705/openapi:latest
Image ID: docker-pullable://us.gcr.io/testproject-175705/openapi@sha256:54b833548cbed32db36ba4808b33c87c15c4ecde673839c3922577f30b
Port: 8080/TCP
State: Terminated
Reason: Error
Exit Code: 143
Started: Thu, 23 Nov 2017 11:50:18 +0000
Finished: Thu, 23 Nov 2017 11:50:35 +0000
Ready: False
Restart Count: 0
Requests:
cpu: 100m
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-61k6c (ro)
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
Volumes:
default-token-61k6c:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-61k6c
Optional: false
QoS Class: Burstable
Node-Selectors: <none>
Tolerations: node.alpha.kubernetes.io/notReady:NoExecute for 300s
node.alpha.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 21s default-scheduler Successfully assigned openapi-7db5f8d479-2d2nm to gke-testproject-default-pool-28ce3836-t4hp
Normal SuccessfulMountVolume 21s kubelet, gke-testproject-default-pool-28ce3836-t4hp MountVolume.SetUp succeeded for volume "default-token-61k6c"
Normal Pulling 21s kubelet, gke-testproject-default-pool-28ce3836-t4hp pulling image "us.gcr.io/testproject-175705/openapi:latest"
Normal Pulled 20s kubelet, gke-testproject-default-pool-28ce3836-t4hp Successfully pulled image "us.gcr.io/testproject-175705/openapi:latest"
Normal Created 20s kubelet, gke-testproject-default-pool-28ce3836-t4hp Created container
Normal Started 20s kubelet, gke-testproject-default-pool-28ce3836-t4hp Started container
Normal Killing 3s kubelet, gke-testproject-default-pool-28ce3836-t4hp Killing container with id docker://openapi:Need to kill Pod
名称:openapi-7db5f8d479-2d2nm
名称空间:默认值
节点:gke-testproject-default-pool-28ce3836-t4hp/10.150.0.2
开始时间:2017年11月23日星期四11:50:17+0000
标签:app=openapi
pod模板哈希=3861948035
注释:kubernetes.io/创建人={“种类”:“SerializedReference”,“apiVersion”:“v1”,“reference”:{“种类”:“ReplicaSet”,“命名空间”:“default”,“name”:“openapi-7db5f8d479”,“uid”:“b7b3e48f-ceb2-11e7-afe7-42010a960003”。。。
io/limit ranger=LimitRanger插件集:容器openapi的cpu请求
状态:终止(截止2017年11月23日星期四11:51:04+0000)
终止宽限期:30秒
知识产权:
创建人:ReplicaSet/openapi-7db5f8d479
控制人:ReplicaSet/openapi-7db5f8d479
容器:
openapi:
容器ID:docker://93d2f1372a7ad004aaeb34b0bc9ee375b6ed48609f505b52495067dd0dcbb233
图片:us.gcr.io/testproject-175705/openapi:latest
图像ID:docker-pullable://us.gcr.io/testproject-175705/openapi@sha256:54b833548cbed32db36ba4808b33c87c15c4ecde673839c3922577f30b
端口:8080/TCP
国家:终止
原因:错误
出境代码:143
开始时间:2017年11月23日星期四11:50:18+0000
完成时间:2017年11月23日星期四11:50:35+0000
就绪:错误
重新启动计数:0
请求:
中央处理器:100米
环境:
挂载:
/来自default-token-61k6c(ro)的var/run/secrets/kubernetes.io/serviceCount
条件:
类型状态
初始化为True
准备错误
播客预定为真
卷数:
default-token-61k6c:
类型:Secret(由Secret填充的卷)
SecretName:default-token-61k6c
可选:false
QoS等级:Burstable
节点选择器:
容差:node.alpha.kubernetes.io/notReady:NoExecute持续300秒
node.alpha.kubernetes.io/不可访问:不执行300秒
活动:
从消息中键入原因年龄
---- ------ ---- ---- -------
正常计划的21s默认计划程序已成功将openapi-7db5f8d479-2d2nm分配给gke-testproject-default-pool-28ce3836-t4hp
正常成功装入卷21s kubelet,gke-testproject-default-pool-28ce3836-t4hp装入卷。卷“default-token-61k6c”的安装成功
正常牵引21s kubelet,gke-testproject-default-pool-28ce3836-t4hp牵引图像“us.gcr.io/testproject-175705/openapi:最新”
正常拉取20s kubelet,gke-testproject-default-pool-28ce3836-t4hp成功拉取图像“us.gcr.io/testproject-175705/openapi:最新”
正常创建20s kubelet,gke-testproject-default-pool-28ce3836-t4hp创建容器
正常启动20s kubelet,gke-testproject-default-pool-28ce3836-t4hp启动容器
正常压井3s kubelet,gke-testproject-default-pool-28ce3836-t4hp压井容器,id为docker://openapi:Need 杀死豆荚
使用以下命令检查pod日志:
kubectl获取事件-w-n命名空间
及
kubectl description pod-n namespace pod\u name
它实际上是说PROJECT\u ID
还是只是为了示例?这只是为了示例。:)添加了事件日志。希望这有助于描述kubernetes正在杀死的podkubectl description pod-n namespace pod\u name
根据您的请求添加了输出。