I'm using Octopus Deploy inside a Kubernetes cluster, however I want to deploy to that cluster as well..

I'm using https://kubernetes.default.svc which is the local endpoint of Kubernetes, typically thats all thats needed as the pod running already has a built-in token used to access Kubernetes via /var/run/secrets/kubernetes.io/serviceaccount/token

https://kubernetes.io/docs/tasks/run-application/access-api-from-pod/

However the UI is complaining "Authentication" is required, so unfortunately, I was required to create another token just to have access.

Can we allow authentication to be optional or an option to use a local cluster?

The audit log is made significantly more difficult to use as edits to a value (in my case, a variable in a variable set, but this likely applies to any array of objects) moves the updated value to the end of the array (deleting and recreating, I would guess).

Ordering the JSON by id before serialising it would make the audit log significantly easier to read, and thus more useful.

in order to determine if a worker can safely be terminated it would be good to have a rest api for this. The closest thing we get today is this script https://github.com/OctopusDeploy/OctopusDeploy-Api/blob/master/REST/PowerShell/Workers/GetWorkersUsedInTasks.ps1 which uses string matching in task log output - very rudimentary, and with tons of failure modes.

I know there's a "worker lease" table, a rest api endpoint covering that table would be great.

I need the ability to add dynamic environments to Octopus Deploy. My use case is Dev Test Lab environments that are spun up and down to run a test suite.