actions-runner-controller: Stuck runners
Hi,
Firstly thank you for the wonderful project. It was much needed. Everything was working well for me before I tried moving my self hosted runners from dev env to production env. Now I have a bunch of runners that I can’t seem to delete:
arhue@hp-laptop:~/git$ kubectl get runners
NAME REPOSITORY STATUS
ga-unittest-6glhx-74d28 tectonic/awardforce
ga-unittest-6glhx-crp9v tectonic/awardforce
ga-unittest-wzj5j-l6r4t tectonic/awardforce
ga-unittest-wzj5j-zmjnd tectonic/awardforce
arhue@hp-laptop:~/git/infrastructure-helm$ kubectl delete runners --force ga-unittest-6glhx-74d28
warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely.
runner.actions.summerwind.dev "ga-unittest-6glhx-74d28" force deleted
^C
I waited almost 10 mins but they didn’t get deleted. This is what my runner deployment looks like:
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
name: ga-unittest
namespace: default
spec:
replicas: 2
template:
spec:
repository: tectonic/awardforce
ImagePullPolicy: Always
image: xxx/infra:actions-runner
resources:
limits:
cpu: "4.0"
memory: "8Gi"
requests:
cpu: "2.0"
memory: "4Gi"
sidecarContainers:
- name: mysql
image: mysql:5.7
env:
- name: MYSQL_ROOT_PASSWORD
value: abcd1234
securityContext:
runAsUser: 0
No pods come up. There seems to be an error in runners:
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedUpdateRegistrationToken 25m (x21 over 64m) runner-controller Updating registration token failed
I tried adding new tokens and app credentials but that change anything. Would like some help on how I can delete the runners created earlier and how I can spin up new ones. Config is managed with helmfile.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 31 (16 by maintainers)
Thanks. I’ll put in a PR in some time. Closing the issue for now. Thank you once again.
@arhue Glad to hear that you finally made it!
Regarding the GitHub App creds and the token, you only need either of them. If you’d like letting the actions-runner-controller to authenticate as a GitHub App, you’d want to give it github_app_{id,installation_id,private_key}.
If you don’t care, using the token alone would be easy to go, which means that you only need
github_token
in the secret.Does this clarify it?
@mumoshu @summerwind Got it! Thank you for your patience and the help. Can I submit a PR to improve the readme docs? I think it is very easy to get confused as things are currently.