[Feature] deployment to 'real' k8s cluster

[fwilhe2]

Describe the feature

I was wondering if anyone tried deploying this to a 'real' k8s cluster and replace the k3s dind solution with using that cluster itself for providing the lab environment?

The other components from the docker compose setup should be reusable, I would assume, did not check which capabilities or permissions they need.

I would imagine that k8s namespaces provide enough isolation so that the ck-x apps could be deployed in their own namespace, and separate task namespaces could be crated automatically to provide various environments for different tasks.

Motivation

• I think it would be interesting to implement this
• This could make SaaS hosting of this solution simpler

Proposed Solution

• convert the compose yaml to k8s manifests
• replace the k8s-api container with interfacing to the deployment cluster
• not sure what else would need to be done

Alternatives considered

none

Additional context

this is just a sunday afternoon thought, have not looked too close into the code or how it could be done. was wondering about prior art on this, feel free to close if the idea is not suitable, I think this could be a nice hackathon project.

Related Issues

[nishanb]

Do you see any improvement over existing deployment staggery, there might be some complexities around DIND mode of the deployment ?