Question

有没有办法知道为什么Kubernetes正在终止豆荚？

如果我在Google控制台中转到Logging，我可以找到与此事件相关的唯一消息是：

shutting down, got signal: Terminated

此外，处于状态Terminating的广告连接永远不会被终止，其中一些已经处于此状态超过24小时。

我没有使用livenessProbes或readinessProbes。

我正在使用terminationGracePeriodSeconds: 30

编辑：截至目前，已将kubectl describe pod <podname>的结果添加到Terminating状态为9小时的广告连播：

Name:               storeassets-5383k
Namespace:          default
Node:               gke-recommendation-engin-default-pool-c9b136a8-0qms/10.132.0.85
Start Time:         Sat, 11 Mar 2017 06:27:32 +0000
Labels:             app=storeassets
                deployment=ab08dc44070ffbbceb69ff6a5d99ae61
                version=v1
Status:             Terminating (expires Tue, 14 Mar 2017 01:30:48 +0000)
Termination Grace Period:   30s
Reason:             NodeLost
Message:            Node gke-recommendation-engin-default-pool-c9b136a8-0qms which was running pod storeassets-5383k is unresponsive
IP:             10.60.3.7
Controllers:            ReplicationController/storeassets
Containers:
  storeassets:
    Container ID:   docker://7b38f1de0321de4a5f2b484f5e2263164a32e9019b275d25d8823de93fb52c30
    Image:      eu.gcr.io/<project-name>/recommendation-content-realtime
    Image ID:       docker://sha256:9e8cf1b743f94f365745a011702a4ae1c2e636ceaaec4dd8d36fef6f787aefe7
    Port:
    Command:
      python
      -m
      realtimecontent.storeassets
    Requests:
      cpu:      100m
    State:      Running
      Started:      Sat, 11 Mar 2017 06:27:33 +0000
    Ready:      True
    Restart Count:  0
    Volume Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-qwfs4 (ro)
    Environment Variables:
      RECOMMENDATION_PROJECT:       <project-name>
      RECOMMENDATION_BIGTABLE_ID:   recommendation-engine
      GOOGLE_APPLICATION_CREDENTIALS:   recommendation-engine-credentials.json
Conditions:
  Type      Status
  Initialized   True
  Ready     False
  PodScheduled  True
Volumes:
  default-token-qwfs4:
    Type:   Secret (a volume populated by a Secret)
    SecretName: default-token-qwfs4
QoS Class:  Burstable
Tolerations:    <none>
No events.

Answer 1

至于pod被终止的原因，一定是因为你的图像/容器正在以成功状态退出。

尝试记录您的pod，直到它退出。你或许可以从那里看到原因。

Kubernetes在日志中没有明确原因终止pod

1 个答案: