Runner

This is currently possible using the CircleCI CLI ( https://support.circleci.com/hc/en-us/articles/15418352844187-How-to-delete-a-Self-Hosted-Runner-Resource-Class ) This request is to enable parity of the same functionality in the Runner UI

To use runner, we went and configured the runner configuration with CircleCI and got dedicated hosts through AWS. We then took the off the shelf AMI and had to add customizations. If there were Circle images for for example if this contains xCode 11.2 - there would be benefit in getting a running macOS image to be able to import.

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

In an effort to be more security conscious by removing the standard shells, it would be great to have a convenience image that includes the Task Agent used by Container Runner.

An ask to open source the self hosted runner agents so the community can work with the team on any issues

It would be nice to be able to set resource constraints for specific images and/or side car containers. The cloud environment will share the resources across your specified resource class when using side car containers.

Request for support in circleci config which will pick a circleci runner if self hosted runner is not available. e.g. Setup single self hosted runner. If it is available then pipeline should run using self hosted runner and if it is not then pipeline should use CircleCI Runner and complete its job. There is a great number of suggestions on this feature request for github actions - https://github.com/orgs/community/discussions/20019 (relevant issue - https://github.com/actions/runner/issues/1969 ) I really like this one: runs-on: - labels: [self-hosted, linux-fast-machine] # try to pick this runner first timeout-minutes: 0 # timeout for such runner - labels: [self-hosted, linux-low-machine] # if not available, pick this runner then timeout-minutes: 0 - labels: [ubuntu-latest] # if above not available, pick this runner last timeout-minutes: 10 A feature like this would be extremely beneficial to startups looking to optimize existing hardware with CircleCI runners as backup.

In some cases, it may be good to surface Container Runner metrics to Prometheus. Such as Task count, Task limit, error logs, etc.

Specifically tools like statsd, Prometheus, etc.

For teams using a number of runners, the UI list can be tedious to scroll through. The ask is to figure out how to make the Runner UI easier to scroll through.