Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

K8s does not automatically create replacement pod. #64

Open
bartoszbinda opened this issue Apr 18, 2023 · 1 comment
Open

K8s does not automatically create replacement pod. #64

bartoszbinda opened this issue Apr 18, 2023 · 1 comment

Comments

@bartoszbinda
Copy link

Hi, I am trying to do exercise 2.4
I did the following
bartoszbinda@MBP-Bartosz dev % docker container ls -q --filter label=io.kubernetes.container.name=hello-kiamol
28e974b049f8
bartoszbinda@MBP-Bartosz dev % docker container rm -f $(docker container ls -q --filter label=io.kubernetes.container.name=hello-kiamol)
28e974b049f8
bartoszbinda@MBP-Bartosz dev % kubectl get pod hello-kiamol
NAME READY STATUS RESTARTS AGE
hello-kiamol 0/1 ContainerStatusUnknown 1 4h17m
bartoszbinda@MBP-Bartosz dev % kubectl get pod hello-kiamol
NAME READY STATUS RESTARTS AGE
hello-kiamol 0/1 ContainerStatusUnknown 1 4h18m
bartoszbinda@MBP-Bartosz dev % docker container ls -q --filter label=io.kubernetes.container.name=hello-kiamol
bartoszbinda@MBP-Bartosz dev % kubectl get pod hello-kiamol
NAME READY STATUS RESTARTS AGE
hello-kiamol 0/1 ContainerStatusUnknown 1 4h18m

as you can see container is in status unknown and replacement was not automatically created as written in a book

@bartoszbinda
Copy link
Author

I think the issue is with restartPolicy=Never, when I removed it (in next pod) it started working

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant