@kylecarbs to add some details here on our plan

Ideally, we allow customers to provide a coder.env file that contains arbitrary environment variables that can be used for configuration. We should not map each configuration value to a key in Helm, as this adds a significant maintenance burden.

This coder.env file would allow customers to arbitrarily pass environment variables too, which seems useful. The container should ship with a PostgreSQL sidecar container, similarly to v1. It should not use the built-in PostgreSQL database, as that would not support high-availability (which is likely to be used for Kubernetes).

Any updated on this?

Any updated on this?

@thalesfsp it is in progress now. Keep a watch on this issue!

This one is currently blocked. @tjcran can you add the items to the comments here around that?

Can we include a setup template for the Kubernetes cluster in the MVP? My thoughts are it's a day of work at most beyond the rest of the feature but makes the whole thing twice as valuable. Bare in mind that our users are looking for the Coder platform entirely on Kubernetes, not just the control plane.

Can we include a setup template for the Kubernetes cluster in the MVP? My thoughts are it's a day of work at most beyond the rest of the feature but makes the whole thing twice as valuable. Bare in mind that our users are looking for the Coder platform entirely on Kubernetes, not just the control plane.

I think that's super reasonable. It won't be "HA" but I think for the <10-15 devs usecase that's just fine.

Can we include a setup template for the Kubernetes cluster in the MVP? My thoughts are it's a day of work at most beyond the rest of the feature but makes the whole thing twice as valuable. Bare in mind that our users are looking for the Coder platform entirely on Kubernetes, not just the control plane.

I think that's super reasonable. It won't be "HA" but I think for the <10-15 devs usecase that's just fine.

@deansheather what are your thoughts on Ammar's suggestion above?

The definition of done in this issue includes running workspaces within the Kubernetes cluster, so I'm reopening.

We currently have a template that runs workspaces as kubernetes containers. https://github.com/coder/coder/tree/main/examples/templates/kubernetes-multi-service

We should probably open a new ticket for having auto-import for a basic Kubernetes "built-in" template.

@ammario @tjcran ^ This should probably be split up into multiple tickets, we already have a separate ticket for HA support #3227. IMO the MVP of the helm chart (being able to deploy coder onto k8s with helm) has already been achieved.

I agree with that. I'll close this one and create an issue for having auto-import for k8s "built-in"