AutoscalingListener doesn't have an owner reference refering to its autoscalingrunnerset

[paul-civitas]

Checks

• I've already read https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors and I'm sure my issue is not covered in the troubleshooting guide.
• I am using charts that are officially provided

Controller Version

0.11.0

Deployment Method

Helm

Checks

• This isn't a question or user support case (For Q&A and community support, go to Discussions).
• I've read the Changelog before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes

To Reproduce

Deploy ARC using argocd. Then it's visually easy to see that owner references haven't been fully implemented yet.

Describe the bug

The autoscalingrunnerset has an associated autoscalinglistener that's its child.

However the controller isn't creating the autoscalinglistener with owner references to the associated autoscalingrunnerset.

If this were to be implemented, it would make it much more clear which autoscalinginglistener relates to which autoscalingrunnerset and also it would make things look much more clear in argocd.

Describe the expected behavior

Owner references exist for autoscalinglisteners.

Additional Context

Can be provided upon request.

Controller Logs

Can be provided upon request.

Runner Pod Logs

Can be provided upon request.

[github-actions]

Hello! Thank you for filing an issue.

The maintainers will triage your issue shortly.

In the meantime, please take a look at the troubleshooting guide for bug reports.

If this is a feature request, please review our contribution guidelines.

[nikola-jokic]

Hey @paul-civitas,

This can't be done properly (see #3575 (comment)). One of the requirements we have is to separate the controller's namespace from the installation namespace. The listener exists in the controllers namespace while the autoscaling runner set exists in the installation namespace. Therefore, the owner reference cannot be set that way.

[paul-civitas]

Understood. Thanks!

[Nastaliss]

@nikola-jokic is merging the two namespaces planned ?
In my case I'm using the same namespace for the controller and the scale set, is there a workaround for me to make the ownerreferences work for listeners ?

[nikola-jokic]

Hey @Nastaliss,

We might change that in future releases, but I cannot say for sure at this time.

[jhychan]

For now, can we have the owner reference conditionally applied if the controller namespace and autoscalingrunnerset namespace are equal? Setting correct owner references when the parent and child exist in the same namespace seems like a reasonable thing to do, without impacting any architectural decisions that may or may not come in the future.