N
N
nafigat2018-06-22 17:37:10
Docker
nafigat, 2018-06-22 17:37:10

There are several docker containers. Where to go next?

Imperceptibly, in a small organization, more than a dozen docker containers have accumulated, mainly for internal use (monitoring, collecting logs, collecting backups, vpn, etc.). Containers are scattered across separate linux hosts. Access to each of them (to the services they provide) is carried out through the host IP address + port on which the corresponding container responds. There is a tendency and a desire to "produce" containers further.
But, I understand that the current situation cannot continue (there is no container mobility, no manageability, the "ip : port = service" list is already large ..). Probably, it is necessary to introduce local DNS into this zoo, maybe orchestration, etc. P...
BUT a concrete understanding of where to move on in principle and what solutions it makes sense to specifically use (so that you don’t have to redo a lot later, etc.) has not yet come.
Is it time to think about Kubernetes?

Answer the question

In order to leave comments, you need to log in

4 answer(s)
I
IOwan, 2018-06-22
@IOwan

Is there no way to merge some containers? Are they all highly specialized and multidirectional?
If not, and there is some kind of interaction between them, then you can think about the Docker Network and somehow combine some of them ..
Even with the union, you will come to Docker Compose.
Is moving all containers to a separate server not an option?) And implementing a local DNS is most likely a matter of time

T
ThemeZV, 2018-06-23
@ThemeZ

If Kubernetes scares you, check out Rancher

A
al_gon, 2018-06-28
@al_gon

If Rancher scares you, look at Portainer

E
Eugene Sai, 2018-06-29
@sol77

I think we should start with this

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question