Support using CODER_AGENT_TOKEN passed through Kubernetes Secret

[strike]

Hi,
I tested coder-logstream-kube in our environment, but it didn’t start correctly.
It seems the software expects CODER_AGENT_TOKEN to be set directly as an environment variable, but in our setup we inject it via a Kubernetes secret like this:

envFrom:
  - secretRef:
      name: secretName

When I tried setting a fake CODER_AGENT_TOKEN manually, I got an authorization error.

We prefer not to pass secrets as pod environment variables, including CODER_AGENT_TOKEN, because it’s less secure — for example, the value could leak into other systems like Prometheus.

Do you have any ideas or plans to support this use case?