We do run kubernetes internally, but do not recommend it for community production projects (yet!). We are in the process of developing CHT 4.0, which will include documentation on installing cht-core on kubernetes along with all the necessary templates (ymls).
For some background info, we currently recommend deploying cht-core on a standalone server with docker (compose) in production. For development, you can also install multiple cht-core versions with docker-compose and our cht installer. I think the latter may resolve most trial use cases. In production projects, Iād recommend using a container orchestrator (k8s) when you are running 8+ projects per server administrator.
Can you describe your use-case:
are you running multiple cht-core deployments in production? Is that the eventual goal?
multiple cht-core deployments for development environments?
running an existing k8s cluster and you wish to add a cht-core pod?
Is it possible to handle your concerns with deploying cht-core using docker-compose and if needed, multiple cht-core versions? Can you wait till CHT 4.0 for k8s support? We anticipate 4.0 to be released in Q1 2022.
I am trying to run CHT on k8 because i would like to set it up on ArgoCD mainly to support our QA functions. This set up is not meant for production use cases as we are already using stand alone instances for our production.
Argocd provides us a way to create multiple pods running CHT-core to test various updates made to our configurations. Once testing is done, we do away with that pod.