Failed calling web hook errors

[szinn]

I've installed the actions-runner-controller on my k3s-based system and have successfully had GitHub trigger a job through the runner. I am not interested in having any kind of web hooks used for scaling etc.

My log is filled with

Feb 10 12:33:44 server-01 k3s[958]: W0210 12:33:44.054006 958 dispatcher.go:176] Failed calling webhook, failing open mutate-runner-pod.webhook.actions.summerwind.dev: failed calling webhook "mutate-runner-pod.webhook.actions.summerwind.dev": failed to call webhook: Post "https://webhook-service.actions-runner-system.svc:443/mutate-runner-set-pod?timeout=10s": dial tcp 10.43.49.46:443: connect: connection refused
Feb 10 12:33:44 server-01 k3s[958]: E0210 12:33:44.054019 958 dispatcher.go:180] failed calling webhook "mutate-runner-pod.webhook.actions.summerwind.dev": failed to call webhook: Post "https://webhook-service.actions-runner-system.svc:443/mutate-runner-set-pod?timeout=10s": dial tcp 10.43.49.46:443: connect: connection refused

and I've noticed the k3s key-value database is filling quickly with updates to the mutating and validating web hook entries. The retries happen so often that the database flooded to the point of bringing the cluster down due to the database being overwhelmed.

I installed this controller using helm with the default values. Is there a configuration setting I can use that does not need cert-manager or try to register web hooks?

Alternatively, can I specify a base name (https://webhook.example.com) for the web hook to be used and then I can wire that up internally to a service in the runner/controller?