Hi, I have a runner running in a pipeline. It runs and deploys into docker in kubernetes when I uploads changed code and it worked fine for a couple of hours ago. But now it failes with the mesage “No matching runner available”. I get the same message when I tries to rerun the job that succeeded a few hours ago. Why do I get this message? Whats wrong?
Best regards
Ingvar
Maybe the jobs use runner tags, and all registered runners are offline or unreachable. Depending on how the runners are registered, either an instance admin, or group owner can inspect and fix the runner status on the server side. Manage runners | GitLab When necessary, the runner side can also shed some light: Troubleshooting GitLab Runner | GitLab
You put me on the track. Since a couple of months we are not a premium customer. The tag we’ve been using is only available to premium customers so I changed it to one available to frugal users 
Strange that gitlab didn’t dismiss this earlier and not cool that they didn’t inform us that we can’t use that tag anymore. But I will certainly not complain about gitlab. We will come back as premium at some point in the future.
Glad you could solve it and sorry for the inconvenience. For GitLab.com, there was a change in 17.0 regarding runner tags, maybe related as well: Removing tags from our small SaaS runner on Linux & A guide to the high-impact breaking changes in GitLab 17.0