1. Kubernetes 常见事件

1.1. 调度失败信息

Message: 0/180 nodes are available: 1 Insufficient cpu, 1 node(s) were unschedulable, 178 node(s) didn't match node selector, 2 Insufficient memory.

消息：0/180个节点可用：1个cpu不足，1个节点不可调度，178个节点与节点选择器不匹配，2个内存不足。

1.2. process_linux.go:319.md

Events:
  Type Reason Age From Message
  ---- ------ ---- ---- -------
  Normal Scheduled 12h default-scheduler Successfully assigned ns1/apitest14bc18 to hangye-online-jda-qz-vm39
  Warning FailedSync 6h32m (x3 over 6h39m) kubelet, hangye-online-jda-qz-vm39 (combined from similar events): error determining status: rpc error: code = Unknown desc = Error: No such container: 0e0d38da603cbec70595406eff3fd0e3754b14f3d58cface6f49d38a25f1e20a
  Normal SandboxChanged 17m (x19490 over 12h) kubelet, hangye-online-jda-qz-vm39 Pod sandbox changed, it will be killed and re-created.
  Warning FailedCreatePodSandBox 2m54s (x19473 over 12h) kubelet, hangye-online-jda-qz-vm39 Failed create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod "apitest14bc18": Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:319: getting the final child's pid from pipe caused \"read init-p: connection reset by peer\"": unknown

这个是由于pod的reources配置错误无法识别导致的

    resources:
      limits:
        cpu: 100m
        memory: "128"
      requests:
        cpu: 100m
        memory: "128"

对于memory的内容需要有单位配置Mi

1.3. Conflict-The-container-name.md

Events:
  Type Reason Age From Message
  ---- ------ ---- ---- -------
  Normal Created 20m (x2 over <invalid>) kubelet, vm172-25-126-20 Created container apigw-redis-sentinel
  Normal Started 20m (x2 over <invalid>) kubelet, vm172-25-126-20 Started container apigw-redis-sentinel
  Warning Failed 18m (x4 over 20m) kubelet, vm172-25-126-20 Error: Error response from daemon: Conflict. The container name "/k8s_apigw-redis-sentinel_apigw-redis-sentinel-1_skiff-apigw_5c6d4be2-98bb-4c1e-a795-04b1a73091a5_3" is already in use by container "7f487468f1d75f6ed211eceaf0f48daa07074ddb98f5de9fa3cdf7d515e5db3d". You have to remove (or rename) that container to be able to reuse that name.
  Warning BackOff 16m (x19 over 21m) kubelet, vm172-25-126-20 Back-off restarting failed container
  Normal Pulled 64s (x75 over <invalid>) kubelet, vm172-25-126-20 Container image "harbor.tp.hwwt2.com/skiff/redis:3.2" already present on machine
  Normal SandboxChanged <invalid> kubelet, vm172-25-126-20 Pod sandbox changed, it will be killed and re-created.

容器名称冲突，停止运行中的容器，然后删除掉该容器

或者 在k8s里面delte pod即可