diff --git a/charts/zeebe-benchmark/templates/publisher.yaml b/charts/zeebe-benchmark/templates/publisher.yaml index 224b98b..1c0eda5 100644 --- a/charts/zeebe-benchmark/templates/publisher.yaml +++ b/charts/zeebe-benchmark/templates/publisher.yaml @@ -23,7 +23,7 @@ spec: - name: JDK_JAVA_OPTIONS value: >- -Dconfig.override_with_env_vars=true - -Dapp.brokerUrl={{ .Release.Name }}-zeebe-gateway:26500 + -Dapp.brokerUrl={{ .Release.Name }}-core:26500 -Dapp.starter.rate={{ .Values.publisher.rate }} -Dzeebe.client.requestTimeout=62000 -XX:+HeapDumpOnOutOfMemoryError diff --git a/charts/zeebe-benchmark/templates/starter.yaml b/charts/zeebe-benchmark/templates/starter.yaml index 57b0d56..52aa10e 100644 --- a/charts/zeebe-benchmark/templates/starter.yaml +++ b/charts/zeebe-benchmark/templates/starter.yaml @@ -26,7 +26,7 @@ spec: {{- if $.Values.saas.enabled }} -Dapp.tls=true {{- else }} - -Dapp.brokerUrl={{ $.Release.Name }}-zeebe-gateway:26500 + -Dapp.brokerUrl={{ $.Release.Name }}-core:26500 {{- end }} -Dapp.starter.rate={{ .Values.starter.rate }} -Dapp.starter.durationLimit=0 diff --git a/charts/zeebe-benchmark/templates/timer.yaml b/charts/zeebe-benchmark/templates/timer.yaml index 0ac4f02..f24f47a 100644 --- a/charts/zeebe-benchmark/templates/timer.yaml +++ b/charts/zeebe-benchmark/templates/timer.yaml @@ -23,7 +23,7 @@ spec: - name: JDK_JAVA_OPTIONS value: >- -Dconfig.override_with_env_vars=true - -Dapp.brokerUrl={{ .Release.Name }}-zeebe-gateway:26500 + -Dapp.brokerUrl={{ .Release.Name }}-core:26500 -Dapp.starter.rate={{ .Values.timer.rate }} -Dzeebe.client.requestTimeout=62000 -XX:+HeapDumpOnOutOfMemoryError diff --git a/charts/zeebe-benchmark/templates/workers.yaml b/charts/zeebe-benchmark/templates/workers.yaml index 077159b..26ef378 100644 --- a/charts/zeebe-benchmark/templates/workers.yaml +++ b/charts/zeebe-benchmark/templates/workers.yaml @@ -27,7 +27,7 @@ spec: {{- if $.Values.saas.enabled }} -Dapp.tls=true {{- else }} - -Dapp.brokerUrl={{ $.Release.Name }}-zeebe-gateway:26500 + -Dapp.brokerUrl={{ $.Release.Name }}-core:26500 {{- end }} -Dzeebe.client.requestTimeout=62000 {{- if $worker.capacity }} diff --git a/charts/zeebe-benchmark/values-realistic-benchmark.yaml b/charts/zeebe-benchmark/values-realistic-benchmark.yaml index 9a3d2b3..bd8b817 100644 --- a/charts/zeebe-benchmark/values-realistic-benchmark.yaml +++ b/charts/zeebe-benchmark/values-realistic-benchmark.yaml @@ -217,95 +217,81 @@ starter: # each created process instance businessKey: "customerId" -camunda-platform: +# ELASTIC +elasticsearch: enabled: true + imageTag: 8.9.2 - zeebe: - # Image configuration to configure the zeebe image specifics - image: - # Image.repository defines which image repository to use - repository: camunda/zeebe - tag: SNAPSHOT - - # Retention can be used to define the data in Elasticsearch (ILM). - retention: - ## @param zeebe.retention.enabled if true, the ILM Policy is created and applied to the index templates. - enabled: true - ## @param zeebe.retention.minimumAge defines how old the data must be, before the data is deleted as a duration. - minimumAge: 1d # set it to a higher value if we run with operate, so operate has enough time to consume the data - - # Resources configuration to set request and limit configuration for the container https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limitsS + master: + fullnameOverride: elastic + nameOverride: elastic + # Number of master-elegible replicas to deploy + replicaCount: 3 + pdb: + minAvailable: 2 + # Elasticsearch master-eligible node heap size. + # Will be converted to -Xms3g + heapSize: 3g + # The resources configurations for elasticsearch containers resources: - limits: - cpu: 1700m - memory: 4Gi requests: - cpu: 1350m - memory: 4Gi + cpu: 1 + memory: 3Gi + limits: + cpu: 2 + memory: 6Gi + persistence: + # Persistent Volume Storage Class + storageClass: "ssd" + # Persistent Volume Size + size: 128Gi + # Persistent Volume Access Modes + accessModes: [ "ReadWriteOnce" ] - zeebeGateway: - # Replicas defines how many standalone gateways are deployed - replicas: 2 - # Image configuration to configure the zeebe-gateway image specifics - image: - # Image.repository defines which image repository to use - repository: camunda/zeebe - tag: SNAPSHOT - # Resources configuration to set request and limit configuration for the container https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits - resources: - limits: - cpu: 450m - memory: 1Gi - requests: - cpu: 450m - memory: 1Gi +## @section Orchestration Core Parameters +## @extra core configuration for the Orchestration Core. +core: + ## @param core.enabled if true, all related resources are deployed via the helm release + enabled: true - operate: - enabled: true - image: - repository: camunda/operate - tag: SNAPSHOT - # Resources configuration to set request and limit configuration for the container https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits - resources: - requests: - cpu: 600m - memory: 400Mi - limits: - cpu: 2000m - memory: 2Gi - env: - - name: CAMUNDA_OPERATE_IMPORTERENABLED - value: "false" + ## @param core.debug if true, extra info is printed. + debug: false + + ## @extra core.image configuration to configure the image specifics + image: + ## @param core.image.repository defines which image repository to use + repository: camunda/camunda + ## @param core.image.tag can be set to overwrite the global tag, which should be used in that chart + tag: SNAPSHOT + + + ## @param core.logLevel defines the log level which is used + logLevel: debug + + ingress: + grpc: + ## @param core.ingress.grpc.enabled if true, an ingress resource is deployed with the Zeebe gateway deployment. Only useful if an ingress controller is available, like nginx. + enabled: true + http: + ## @param core.ingress.http.enabled if true, an ingress resource is deployed with the Zeebe gateway deployment. Only useful if an ingress controller is available, like nginx. + enabled: true - # ELASTIC - elasticsearch: - enabled: true - imageTag: 8.9.2 + ## @extra core.resources configuration to set request and limit configuration for the container https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits + ## @extra core.resources.requests + ## @param core.resources.requests.cpu + ## @param core.resources.requests.memory + ## @param core.resources.limits.cpu + ## @param core.resources.limits.memory + resources: + requests: + cpu: 1350m + memory: 4Gi + limits: + cpu: 1700m + memory: 4Gi - master: - fullnameOverride: elastic - nameOverride: elastic - # Number of master-elegible replicas to deploy - replicaCount: 3 - pdb: - minAvailable: 2 - # Elasticsearch master-eligible node heap size. - # Will be converted to -Xms3g - heapSize: 3g - # The resources configurations for elasticsearch containers - resources: - requests: - cpu: 1 - memory: 3Gi - limits: - cpu: 2 - memory: 6Gi - persistence: - # Persistent Volume Storage Class - storageClass: "ssd" - # Persistent Volume Size - size: 128Gi - # Persistent Volume Access Modes - accessModes: [ "ReadWriteOnce" ] +prometheusServiceMonitor: + ## @param prometheusServiceMonitor.enabled if true then a service monitor will be deployed, which allows an installed prometheus controller to scrape metrics from the deployed pods + enabled: true \ No newline at end of file