From db92c33706ee52feb638c1046478ee0627a774f2 Mon Sep 17 00:00:00 2001 From: Michael Ruoss Date: Thu, 10 Oct 2024 21:27:45 +0200 Subject: [PATCH] Add troubleshooting --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index 0d85b58..77e8363 100644 --- a/README.md +++ b/README.md @@ -151,3 +151,13 @@ information from the running Pod like the container image, resource requests and limits, environment variables etc. This information is then used to build the manifest for the runner pod. The backend then sends the resulting manifest to the API server in order to spin up a runner pod. + +## Troubleshooting + +### My runner Pod disappears / gets killed after only a few seconds + +If your parent is part of a Deployment, make sure your FLAME runner Pod doesn't +contain the labels you used as selectors (i.e. `.spec.selector` on your +Deployment). Otherwise the replica controller sees your FLAME runner as an +additional Pod to the Deployment's ReplicaSet and "downscales" the deployment to +the desired replica count (i.e. snipes your runner Pod).