Question 84981 in Docker Question posted in
The official documentation can be found here.

K8s: deployment patterns for node.js apps with dbs – Docker

Hi!

My problem is relevant with the deployment of node.js apps via k8s, architecture patterns, and connected them with DBs.

 alpha | beta | gamma1 | gamma2

I have the following node.js app services, some of them are scalable with app instances (like gamma), others are separate ones, all of them are built in a single docker image with .Dockefile and running from it.

And I also have a-non-cloud DBs, like elastic & mongo running from their containers with .env: mongo | elastic

As for now, my docker-compose.yml is like a typical node.js example app, but with common volume and bridge-network (except I have more then one node.js app):

version: '3'
services:
  node:
    restart: always
    build: .
    ports:
      - 80:3000
    volumes:
      - ./:/code
  mongo:
    image: mongo
    ports:
      - 27017:27017
    volumes:
      - mongodb:/data/db
volumes:
 mongodb:

networks:
  test-network:
    driver: bridge

Current deployment:

All these things are running on a single heavy VPS (X CPU cores, Y RAM, Z SSD, everything loaded by 70%) from single docker-compose.yml file.

What I want to ask and achieve:

Since one VPS is already not enough, I’d like to start using k8s with rancher. So the question is about correct deployment:

For example, I have N VPSs connected within one private network, each VPS is a worker connected in one cluster, (with Rancher, of course, one of them is a master node) which gives me X cores, Y RAM, and other shared resources.

  1. Do I need another, separate cluster (or a VPS machine in a private network, but not part of a cluster) with DB running on it? Or I could deploy DB in the same cluster? And what if each VPS (worker) in the cluster has only 40GB volume, and DB will grow more than this volume? Do shared resources from workers include the shared volume space?

  2. Is it right to have one image from which I can start all my apps, or in the case of k8s, I should I have a separate docker image for each service? So if I have 5 node.js apps within one mono-repo, I should have 5 separate docker-image, not one common?

I’ll understand that my question can have a complex answer, so I will be glad to see, not just answer but links or anything that is connected with a problem. It’s much more easy to find or google for something, if you know and how to ask.

Tags:

2

Answers


  1. 0

    I can’t answer the part of your question about the VPS machine setup, but I can make some suggestions about the image setup.

    Actually, while you have asked this question about a node app, it’s actually applicable for more than just node.

    Regarding the docker image and having a common image or separate ones; generally it’s up to you and/or your company as to whether you have a common or separate image.

    There’s both pros and cons about both methods:

    You could "bake in" the code into the image, and have a different image per app, but if you run into any security vulnerabilities, you have to patch, rebuild, and redeploy all the images. If you had 5 apps all using the same library, but that library was not in the base image, then you would have to patch it 5 times, once in each image, rebuild the image and redeploy.

    Or you could just use a single base image which includes the libraries needed, and mount the codebase in (for example as a configmap), and that base image would never need to change unless you had to patch something in the underlying operating system. The same vulnerability mentioned in the paragraph above, would only need to be patched in the base image, and the affected pods could be respun (no need to redeploy).

    Login or Signup to reply.
  2. 0

    A purist answer:

    Each of your five services should have their own image, and their own database. It’s okay for the databases to be in the same cluster so long as you have a way to back them up, run migrations, and do other database-y things. If your cloud provider offers managed versions of these databases then storing the data outside the cluster is fine too, and can help get around some of the disk-space issues you cite.

    I tend to use Helm for actual deployment mechanics as a way to inject things like host names and other settings at deploy time. Each service would have its own Dockerfile, its own Helm chart, its own package.json, and so on. Your CI system would build and deploy each service separately.

    A practical answer:

    There’s nothing technically wrong with running multiple containers off the same image doing different work. If you have a single repository and a single build system now, and you don’t mind a change in one service causing all of them to redeploy, this approach will work fine.

    Whatever build system your repository has now, if you go with this approach, I’d put a single Dockerfile in the repository root and probably have a single Helm chart to deploy it. In the Helm chart Deployment spec you can override the command to run with something like

    # This fragment appears under containers: in a Deployment's Pod spec
# (this is Helm chart, Go text/template templated, YAML syntax)
image: {{ .Values.repository }}/{{ .Values.image }}:{{ .Values.tag }}
command: node service3/index.js

    Kubernetes’s terminology here is slightly off from Docker’s, particularly if you use an entrypoint wrapper script. Kubernetes command: overrides a Dockerfile ENTRYPOINT, and Kubernetes args: overrides CMD.

    In either case:

    Many things in Kubernetes allocate infrastructure dynamically. For example, you can set up a horizontal pod autoscaler to set the replica count of a Deployment based on load, or a cluster autoscaler to set up more (cloud) instances to run Pods if needed. If you have a persistent volume provisioner then a Kubernetes PersistentVolumeClaim object can be backed by dynamically allocated storage (on AWS, for example, it creates an EBS volume), and you won’t be limited to the storage space of a single node. You can often find prebuilt Helm charts for the databases; if not, use a StatefulSet to have Kubernetes create the PVCs for you.

    Make sure your CI system produces images with a unique tag, maybe based on a timestamp or source control commit ID. Don’t use ...:latest or another fixed string: Kubernetes won’t redeploy on update unless the text of the image: string changes.

    Multiple clusters is tricky in a lot of ways. In my day job we have separate clusters per environment (development, pre-production, production) but the application itself runs in a single cluster and there is no communication between clusters. If you can manage the storage then running the databases in the same cluster is fine.

    Several Compose options don’t translate well to Kubernetes. I’d especially recommend removing the volumes: that bind-mount your code into the container and validating your image runs correctly, before you do anything Kubernetes-specific. If you’re replacing the entire source tree in the image then you’re not really actually running the image, and it’ll be much easier to debug locally. In Kubernetes you also have almost no control over networks: but they’re not really needed in Compose either.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search