Pod reset

[yennym3]

Hi, If it happens that a pod is evicted from the node because it was running out of ephemeral storage resources, how can the pod be configured so that the pod can be restarted using kne

[alexmasi]

So in this case you were creating a kne HOST node with the alpine:latest container image. However when creating the topo, the k8 node did not have enough storage. But it appears the image was in fact later pulled (did the k8 node gain more resources? or is this using kind?). Then after the image was pulled the pod creation was never retried?

[yennym3]

So in this case you were creating a kne HOST node with the alpine:latest container image. However when creating the topo, the k8 node did not have enough storage. But it appears the image was in fact later pulled (did the k8 node gain more resources? or is this using kind?). Then after the image was pulled the pod creation was never retried?

Sorry, it was solved by giving more disk storage resources on the k8s node.

I have another question I would like to ask you, kne allows to add a new router (pod) to an interface of a pod already created in a scenario that was already deployed? Without having to destroy or redeploy the topology previously created to add this new pod, making use of a multinode cluster.

[alexmasi]

There is no way to do this currently. There may be some hacky way you can apply extra yaml to do this, but it is not supported in the kne cli.