Managed Kubernetes service-old - All pods killed and to "Container Creating"
... / All pods killed and to "C...
< Previous question   -   Next question >
BMPCreated with Sketch.BMPZIPCreated with Sketch.ZIPXLSCreated with Sketch.XLSTXTCreated with Sketch.TXTPPTCreated with Sketch.PPTPNGCreated with Sketch.PNGPDFCreated with Sketch.PDFJPGCreated with Sketch.JPGGIFCreated with Sketch.GIFDOCCreated with Sketch.DOC Error Created with Sketch.
Frage

All pods killed and to "Container Creating"

G
Von
GuillaumeL30
Erstellungsdatum 2019-02-13 10:11:56 (edited on 2024-09-04 13:18:55) in Managed Kubernetes service-old

Hi,

Since it's the third it's happenning to me, I'll request some help from OVH team about a big issue I got.

I have a managed k8s cluster with 1 node used for CI/CD. All is going well with container creation and running. Then suddenly all pods are out and change to "ContainerCreating" :

image

I check the nodes :

image

First hint, the "Age" of 18h seems odd, since I created the node some days ago. Then I check some more info on the node :

image
image

Every thing seems here also fine but nothing's running on the cluster ...

When I try to gather some info on a "base service" pod :

image
image
image
image

So what I suspect is that the node was "re-created" at some point but all local storage and mount points were not correctly transferred.

The only way I have on fixing that is to delete the node and creating one new (with all configurations adjustments needed).

Could you help ?

Thanks
Positive Bewertungen (0)
5771 Ansichten
2 Antworten ( Latest reply on 2019-02-13 11:08:01 Von
GuillaumeL30
)
N

Hi,

It looks like you 'manually' renamed your Public cloud instances after node creation.

This is a known problem that causes issues with node interaction with the control plane (node is unable to access needed resources like tokens, etc)

This is a bit akward to detect it on our side because , as you pointed out, the node is in ready state.
But we are working on the issue, and will communicate once it is resolved.

In the meantime, you are already able to name your nodes at creation when using the OVH API (You will soon be able to do it when using the OVH Manager).

We hope this helps, and are sorry for the inconvenience.

Have a nice day
Hilfreich (0)
G

Hi NicoN,

Thanks for the quick answer. I was really not expecting such an explanation. But the solution's simple : I won't rename my nodes ;)

Thanks a lot
Hilfreich (0)
Antworten sind derzeit für diese Frage deaktiviert.

Related questions

An Diskussion teilnehmen