Answer the question
In order to leave comments, you need to log in
Do I need k8s?
Now such an infrastructure: 2 cheap VPS and 3 local sites with various services inside, which are combined into one network through an openvpn server on one of the VPS. As the network grows, it becomes quite difficult to monitor the health of the network.
After I transferred almost services to docker, it became much easier: I made the launch of containers through docker-compose. Now, even in the case of a server relocation or reinstallation, the configuration has been simplified: I install a docker compose on a new machine and throw the config there. But I still want some more reliable solution and an automated solution, since I have to go to the hosts via ssh, tweaking the configs and setting up monitoring and collecting logs. It is not clear yet whether node cubers will be available in different subnets that connect via openvpn?
Answer the question
In order to leave comments, you need to log in
In the case of the cube, I advise you to think a lot. It just seems like life will get easier. To deploy your services, it will no longer be enough to write a Dockerfile and docker-compose.yml. You will have to add cube configurations for each service, or helm charts. Plus, it will eat additional resources from your VPS. Plus, you will need to deal with all its essences and pitfalls. Learn kubectl. In general, if you are not going to real clouds (amazon, google, azure) to scale wildly and that's all - I would not recommend the cube. There will be more hemorrhoids.
for k8s, two cheap vps will be rather weak, it makes sense to start with swarm, for example
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question