---apiVersion:v1kind:Podmetadata:name:broken-pod-multi-container-no-command-podspec:containers:# this container has no command or entrypoint specified-image:mstormo/suseimagePullPolicy:IfNotPresentname:broken-pod-multi-container-no-command-1-image:busyboxcommand:-sleep-"3600"name:broken-pod-multi-container-no-command-2
no-command.yaml
---apiVersion:v1kind:Podmetadata:name:broken-pods-no-command-podspec:containers:# this container has no command or entrypoint specified-image:mstormo/susename:broken-pods-no-command-container
oom-killed.yaml
---# https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/ claims that this invoked the OOM killer, but it runs fine on MicroK8s?apiVersion:v1kind:Podmetadata:name:broken-pods-oom-killed-podspec:containers:-args:["--vm","1","--vm-bytes","250M","--vm-hang","1"]command:["stress"]image:polinux/stressname:broken-pods-oom-killed-containerresources:limits:memory:"100Mi"requests:memory:"50Mi"
private-repo.yaml
---apiVersion:v1kind:Podmetadata:name:broken-pods-private-repo-podspec:containers:# this container has no command or entrypoint specified-image:imiell/bad-dockerfile-privatename:broken-pods-private-repo-container
too-much-mem.yaml
---# https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/ claims that this invoked the OOM killer, but it runs fine on MicroK8s?apiVersion:v1kind:Podmetadata:name:broken-pods-too-much-mem-podspec:containers:-command:-sleep-"3600"image:busyboxname:broken-pods-too-much-mem-containerresources:requests:memory:"1000Gi"