Listener does not start

[CommissarClippy]

PS C:\Users\Administrator> helm list -A
NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                                   APP VERSION
arc             arc-systems     1               2024-03-06 14:47:26.0230607 +0100 CET   deployed        gha-runner-scale-set-controller-0.8.3   0.8.3
arc-runner-set  arc-runners     1               2024-03-06 14:50:29.0405915 +0100 CET   deployed        gha-runner-scale-set-0.8.3              0.8.3

PS C:\Users\Administrator> kubectl get pods --namespace arc-systems
NAME                                     READY   STATUS    RESTARTS   AGE
arc-gha-rs-controller-7fcd65b66b-wsnv2   1/1     Running   0          72m

PS C:\Users\Administrator> kubectl describe pods arc-gha-rs-controller-7fcd65b66b-wsnv2 -n arc-systems
Name:             arc-gha-rs-controller-7fcd65b66b-wsnv2
Namespace:        arc-systems
Priority:         0
Service Account:  arc-gha-rs-controller
Node:             minikube/192.168.178.23
Start Time:       Wed, 06 Mar 2024 14:47:26 +0100
Labels:           app.kubernetes.io/component=controller-manager
                  app.kubernetes.io/instance=arc
                  app.kubernetes.io/name=gha-rs-controller
                  app.kubernetes.io/namespace=arc-systems
                  app.kubernetes.io/part-of=gha-rs-controller
                  app.kubernetes.io/version=0.8.3
                  pod-template-hash=7fcd65b66b
Annotations:      kubectl.kubernetes.io/default-container: manager
Status:           Running
IP:               10.244.0.6
IPs:
  IP:           10.244.0.6
Controlled By:  ReplicaSet/arc-gha-rs-controller-7fcd65b66b
Containers:
  manager:
    Container ID:  docker://1ea9cbeaa22df850f512bc4532ff2eebbbf8e7e8d754d1da2c4a999bffc9dfff
    Image:         ghcr.io/actions/gha-runner-scale-set-controller:0.8.3
    Image ID:      docker-pullable://ghcr.io/actions/gha-runner-scale-set-controller@sha256:3e74b4967fc585bc3bf2f544a96b4826135738be3962224a2ca9a855e604fb15
    Port:          <none>
    Host Port:     <none>
    Command:
      /manager
    Args:
      --auto-scaling-runner-set-only
      --log-level=debug
      --log-format=text
      --update-strategy=immediate
      --listener-metrics-addr=0
      --listener-metrics-endpoint=
      --metrics-addr=0
    State:          Running
      Started:      Wed, 06 Mar 2024 14:47:35 +0100
    Ready:          True
    Restart Count:  0
    Environment:
      CONTROLLER_MANAGER_CONTAINER_IMAGE:  ghcr.io/actions/gha-runner-scale-set-controller:0.8.3
      CONTROLLER_MANAGER_POD_NAMESPACE:    arc-systems (v1:metadata.namespace)
    Mounts:
      /tmp from tmp (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-lfb9x (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  tmp:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  kube-api-access-lfb9x:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:                      <none>

As stated in the troubleshooting guid in the quick start guide I should check the log of the controller if the listener does not start. The log does not show anything strange (as far as I can tell). Next step would be to check connection to the kubernetes API, however I am not sure how to do this. I tried the following command as found on the internet, but without succes.

kubectl exec arc-gha-rs-controller-7fcd65b66b-wsnv2 --namespace=arc-systems -- curl -s --fail http://kubernetes.default.svc.cluster.local

Paragraph from Troubleshooting guide (https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors)
[Troubleshooting the listener pod](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors#troubleshooting-the-listener-pod) If the controller pod is running, but the listener pod is not, inspect the logs of the controller first and see if there are any errors. If there are no errors and the runner set listener pod is still not running, ensure the controller pod has access to the Kubernetes API server in your cluster.

Any advice on how to fix?