AutoDevOps Helm Chart Multiple Containers

Hello together,

Currently I am depoying a node app which consists of 3 (4) different docker containers. Each one is build with one dockerfile, but the are started with different npm commands.

  • npm start backend
  • npm start messaging
  • npm start scheduler

So for Kubernetes I would pass backend, messaging or scheduler to as an argument to the pod.
But with the AutoDevOps Helm Chart I only got one deployment.

How do you handle sth. like this? “Forking” the chart an adding additional deployment manifest templates?

Maybe there are some of you having some experiences with this kind of deployments.

Regards,

Dominic

Hi,
Just ran across this and wondered if you found a solution to this.

Havent tried yet myself, but i’d look into inheriting gl-ci.yaml from autodevops and then defining additional steps in deploy stage, following how it’s done here for the build step Auto Build for multiple Docker containers - #3 by dbarbarisi

also there’s this Guided Explorations / DevOps Patterns / Multi Container Monorepo Using AutoDevOps · GitLab