Kubernetes 如何在OpenShift中调试崩溃循环吊舱？

我有一个简单的DeploymentConfig：

apiVersion: v1
kind: DeploymentConfig
metadata:
  name: my-dc
  labels:
    app: my
spec:
  replicas: 3
  template:
    metadata:
      labels:
        app: my
    spec:
      containers:
        - name: my
          image: image-registry.openshift-image-registry.svc:5000/pc/rhel-atomic
          livenessProbe:
            exec:
              command:
                - echo
                - "I'm alive!"
              initialDelaySeconds: 10
          readinessProbe:
            exec:
              command:
                - echo
                - "I'm healthy!"
              initialDelaySeconds: 15
              periodSeconds: 15

image registry.openshift image registry.svc:5000/pc/rhel-atomic

图像流指向我自己的图像，即：

FROM registry.access.redhat.com/rhel7/rhel-atomic

当我创建-f my dc.yaml并尝试检查发生了什么时，我发现我的pod正在崩溃循环

为了调试它，我做了一个

ocstatus--suggest

。它建议使用

oc logs my-dc-1-z889c-c my

列出容器日志。但是，没有任何容器的日志

My

oc get events

也没有帮助。它只是循环浏览这些消息：

<unknown>   Normal    Scheduled                     pod/my-dc-1-vnhmp                     Successfully assigned pc/my-dc-1-vnhmp to ip-10-0-128-37.ec2.internal
31m         Normal    Pulling                       pod/my-dc-1-vnhmp                     Pulling image "image-registry.openshift-image-registry.svc:5000/pc/rhel-atomic"
31m         Normal    Pulled                        pod/my-dc-1-vnhmp                     Successfully pulled image "image-registry.openshift-image-registry.svc:5000/pc/rhel-atomic"
31m         Normal    Created                       pod/my-dc-1-vnhmp                     Created container my
31m         Normal    Started                       pod/my-dc-1-vnhmp                     Started container my
27m         Warning   BackOff                       pod/my-dc-1-vnhmp                     Back-off restarting failed container
<unknown>   Normal    Scheduled                     pod/my-dc-1-z8jgb                     Successfully assigned pc/my-dc-1-z8jgb to ip-10-0-169-70.ec2.internal
31m         Normal    Pulling                       pod/my-dc-1-z8jgb                     Pulling image "image-registry.openshift-image-registry.svc:5000/pc/rhel-atomic"
31m         Normal    Pulled                        pod/my-dc-1-z8jgb                     Successfully pulled image "image-registry.openshift-image-registry.svc:5000/pc/rhel-atomic"
31m         Normal    Created                       pod/my-dc-1-z8jgb                     Created container my
31m         Normal    Started                       pod/my-dc-1-z8jgb                     Started container my
27m         Warning   BackOff                       pod/my-dc-1-z8jgb                     Back-off restarting failed container

Normal Scheduled pod/my-dc-1-vnhmp成功地将pc/my-dc-1-vnhmp分配给ip-10-0-128-37.ec2.internal
31m普通拉入吊舱/my-dc-1-vnhmp拉入映像“映像注册表.openshift映像注册表.svc:5000/pc/rhel原子”
31m正常拉入pod/my-dc-1-vnhmp成功拉入图像“image registry.openshift image registry.svc:5000/pc/rhel-atomic”
31m普通创建的pod/my-dc-1-vnhmp创建的容器my
31m正常启动吊舱/my-dc-1-vnhmp启动集装箱my
27m警告后退吊舱/my-dc-1-vnhmp后退重启失败容器
正常计划pod/my-dc-1-z8jgb已成功将pc/my-dc-1-z8jgb分配给ip-10-0-169-70.ec2.1内部
31m普通牵引吊舱/my-dc-1-z8jgb牵引图像“图像注册表。openshift图像注册表。svc:5000/pc/rhel原子”
31m正常拉入pod/my-dc-1-z8jgb成功拉入图像“图像注册表。openshift图像注册表。svc:5000/pc/rhel原子”
31m普通创建吊舱/my-dc-1-z8jgb创建容器my
31m正常启动吊舱/my-dc-1-z8jgb启动集装箱my
27m警告后退吊舱/my-dc-1-z8jgb后退重启失败容器

如何调试这个？集装箱为什么会坠毁

---

我正在使用OpenShift Online。

pod中的单个容器似乎没有运行任何进程。因此，容器在启动后立即终止

保持容器运行的一个选项是将以下内容添加到容器的DeploymentConfig中：

        command:
        - /bin/sh
        stdin: true

---

使用不同的外壳（例如bash）替换

/bin/sh

，或者根据图像中的可用内容从不同的位置替换。

kubectl get的输出events@ArghyaSadhu它并不比我在web控制台中看到的更好。看看最新的问题。是的，就是这样。这是我的一个非常愚蠢的错误