This is indeed something our documentation lacks currently. About production deployment there are couple of ways we can look at it -
We are testing and soon will be made publicly available the kool cloud deploy commands, which basically will look into translating your local docker-compose.yml to a Kubernetes deployment - leveraging our already open source Helm charts. We hope to build some sort of service around it too.
What we have done in the past and we see people doing somewhat often, althoug it's not the optimal usage, is adapting the docker-compose.yml file extending it to production (add restart, change the image to a production optimized one if suitable, and even add resources control/change port mapping accordingly). This solution already helps a lot of folks that will be running the same env they do for development, to production, making easier to manage both at the same time. But there are problems of course, observability/scaling, putting it all togheter still needs manual steps. That is why we will be focusing and releasing the Kubernetes deploy option I mentioned above soon, to be the "go to" solution for deployment.
Other options like AWS ECS, are options we certianly wanna help people with too.
So our goal is, while focusing on the option number 1 to enable the community and companies leverage Kubernetes today, going really "cloud native", we certainly want to document and offer help with the other two options. Our documention is a big Work in Progress and we will soon be covering these options. As well as the Dockerfile creation, which is needed in all of the options above.
The initial good response we are having with this post will make us run faster with all of this. In case someone wanna join and help feel free to join our Slack to discuss/get help or get a PR up on Github!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is indeed something our documentation lacks currently. About production deployment there are couple of ways we can look at it -
We are testing and soon will be made publicly available the
kool cloud deploycommands, which basically will look into translating your localdocker-compose.ymlto a Kubernetes deployment - leveraging our already open source Helm charts. We hope to build some sort of service around it too.What we have done in the past and we see people doing somewhat often, althoug it's not the optimal usage, is adapting the
docker-compose.ymlfile extending it to production (addrestart, change the image to a production optimized one if suitable, and even add resources control/change port mapping accordingly). This solution already helps a lot of folks that will be running the same env they do for development, to production, making easier to manage both at the same time. But there are problems of course, observability/scaling, putting it all togheter still needs manual steps. That is why we will be focusing and releasing the Kubernetes deploy option I mentioned above soon, to be the "go to" solution for deployment.Other options like AWS ECS, are options we certianly wanna help people with too.
So our goal is, while focusing on the option number 1 to enable the community and companies leverage Kubernetes today, going really "cloud native", we certainly want to document and offer help with the other two options. Our documention is a big Work in Progress and we will soon be covering these options. As well as the
Dockerfilecreation, which is needed in all of the options above.The initial good response we are having with this post will make us run faster with all of this. In case someone wanna join and help feel free to join our Slack to discuss/get help or get a PR up on Github!