New AutoscalingRunnerSet - Failed to get runner scale set from Actions service

Checks

• I've already read https://github.com/actions/actions-runner-controller/blob/master/TROUBLESHOOTING.md and I'm sure my issue is not covered in the troubleshooting guide.
• I'm not using a custom entrypoint in my runner image

Controller Version

2

Helm Chart Version

0.1.0

CertManager Version

No response

Deployment Method

Helm

cert-manager installation

cert manager is installed and working, though as I understand not required for v2

Checks

• This isn't a question or user support case (For Q&A and community support, go to Discussions. It might also be a good idea to contract with any of contributors and maintainers if your business is so critical and therefore you need priority support
• I've read releasenotes before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes
• My actions-runner-controller version (v0.x.y) does support the feature
• I've already upgraded ARC (including the CRDs, see charts/actions-runner-controller/docs/UPGRADING.md for details) to the latest and it didn't fix the issue
• I've migrated to the workflow job webhook event (if you using webhook driven scaling)

Resource Definitions

I'm using the standard helms from 
https://github.com/actions/actions-runner-controller/blob/f9bae708c2e06b4cb2d4ed8844f4eb12a09e7c16/docs/preview/actions-runner-controller-2/README.md

To Reproduce

install controller per documentation
install autoscaling runnerset per documentation using helm and app installation method

kubectl get pods
No resources found in arc-runner-set namespace.

### Describe the bug

Listener pod does not start as documented

### Describe the expected behavior

Pods should start

### Whole Controller Logs

```shell
https://gist.github.com/davidsielert/e00a0d7414e3d58d7e0e2612642a6ac0

Whole Runner Pod Logs

n\a

Additional Context

I acknowledge Documentation does state

This mode is currently only available for a limited number of organizations.

What does this even mean?

Start with the preview AutoscalingRunnerSet documentation at docs/preview/actions-runner-controller-2/README.md and reproduce the Helm installation described there with kubectl. Compare the controller behavior with the linked controller logs and verify that the listener and runner pods start as documented without the reported Actions service error.