camunda-helm node option? about camunda-7-community-helm HOT 6 CLOSED

Hi @eins
I believe that it is an application config, is it?

Could you please give more details about the exact option/config apart from the chart itself?

from camunda-7-community-helm.

I couldn't find a way to pass the current camunda docker tag for run 7.15.0

# image settings
image:
  repository: camunda/camunda-bpm-platform
  tag: run-7.15.0
metrics:
  enabled: false

It looks like camunda-helm only lunch a pod. I want to see if we can lunch three pods one for the camunda-core with the connection the the db and then two or three pods for webapps, rest and swaggerui

from camunda-7-community-helm.

@eins the new version of the chart v1.0.0 supports that via passing different args to the deployment.

You can see here the exact example where you can create rest only deployment:
https://github.com/camunda-community-hub/camunda-helm/tree/36a1ca6/charts/camunda-bpm-platform#example

from camunda-7-community-helm.

@aabouzaid thanks for the reply
Do you know if it is possible the change the image repository ?
camunda/camunda-bpm-platform

image:
  #  repository: camunda/camunda-bpm-platform
  repository: wwwwwww.dkr.ecr.eu-central-1.amazonaws.com/repo101:cee7.15.4
  tag: run

I got InvalidImageName and ImagePullBackOff errors

from camunda-7-community-helm.

@eins you added the tag into repository
it should be like this, and you need to setup imagePullSecrets

image:
  repository: wwwwwww.dkr.ecr.eu-central-1.amazonaws.com/repo101
  tag: cee7.15.4
  pullSecrets:
    - DOCKER_CONFIG_JSON_SECRET

from camunda-7-community-helm.

Since this issue has been fixed by v1.0.0, I'm closing it.

from camunda-7-community-helm.