Support macOS on Container Runner
This feature request is to support building ios apps/macOS on container runner. Currently, macOS is only supported on machine runner
Support Windows Containers On Container Runner
For jobs that need to be run internally with Windows containers, having to maintain multiple Windows nodes for machine runners can be expensive and they are not easily auto-scaled leading to idle time. Having the ability to orchestrate windows containers via container runner would greatly reduce the overhead required for running such containers.
Provide metrics to Prometheus from Container Runner
In some cases, it may be good to surface Container Runner metrics to Prometheus. Such as Task count, Task limit, error logs, etc.
Increase the timeout of livenessProbe and readinessProbe
To help with network congestion and throughput, it would be great if we could increase this timeout to better counter networks that are congested or take time to spin up.
Add Support for Karate Test Framework Reports
CircleCI has an impressive range of tools supported for uploading test results, but Karate is not in that list. The options provided(Maven, or artifact upload), do not provide a tab where the user can navigate to and immediately see test results. As Karate generates an HTML report by default, adding better HTML integration would be a great way to go, an integration that does not require sifting through all the files used to generate the report, but simply consumes those files, and generates the report directly.
Allow orgs to opt-in to allow OSS forked jobs on Runner
Creating this to track an ask from several OSS orgs. There is a desire to allow OSS fork jobs on their runner executors.
Be able to set resource limits/requests per service container for self hosted container runner
In a self hosted scenario, using container runner (kubernetes setup) and service containers, it would be great if you can specify different resource limits/requests instead of inheriting these specs from the first container. The current limitation causes a lot of resource waste
Develop a better way for Container Runner to clean up failed task pods
In some cases, container runner fails to clean up dead task pods before the GC loop takes effect. It would be great if the team can explore other options so as to allow rely on the GC loop as a fail back and decrease cluster resource needs.
Open source the self hosted runner agents
An ask to open source the self hosted runner agents so the community can work with the team on any issues