We’re trying to run self-hosted runners inside our kubernetes cluster, it worked fine until our image didn’t contain the latest runner: Runner update in progress, do not shutdown runner. Downloading 2.161.0 runner Waiting for current job finish running. Generate and execute update script. Runner will exit shortly for update, should back online within 10 seconds. I know that runner will automatically update to latest version and exit for a while. However, this update would fail every time and exit, resulting in kubernetes spinning up another Pod, which finally we see an infinite loop. Is there an option to disable such behavior in ./run.sh?
... View more