-
**Describe the issue:**
Always get
```
coalesce.go:223: warning: destination for identity.postgresql.networkPolicy.egressRules.customRules is a table. Ignoring non-table value ([])
coalesce.go…
-
**Describe the bug**
I am adding hazelcast exporter the "Adding dynamic exporters to Zeebe Broker" - way, using Helm charts into Kubernetes. This works in 8.2.9 and not in 8.3.0.
The error is w…
-
Output of `helm version`: v3.12.1
Output of `kubectl version`: 1.23
Cloud Provider/Platform (A…
-
Hi,
I'm a beginner in Camunda. When installing the camunda I got this error. Can anyone help on this?
```
helm install --name camunda ./camunda-platform/
helm3 install --name camunda ./camunda…
-
**Describe the issue:**
When Installing C8 with the 8.3.1 Helm Release, I face the following warnings:
```
coalesce.go:223: warning: destination for identity.postgresql.networkPolicy.egressRule…
-
**Describe the issue:**
Camunda Self-Hosted on EKS cluster in AWS. Configuration is done as below but it's used a proposed one by Camunda.
**Actual behavior:**
I open https://optimize-camunda.e…
-
After or during #125 we should make sure to migrate to ILM and configure it correctly.
Important to note is that we need to check how we handle old runs, for old releases.
-
The gateway now has a new configuration flag to enable multi-tenancy:
- `zeebe.gateway.multiTenancy.enabled`
- `zeebe.broker.gateway.multiTenancy.enabled`
The helm charts must be updated: https:/…
-
**Describe the issue:**
When we do helm install with
```
zeebe-gateway:
env:
- name: ZEEBE_GATEWAY_SECURITY_AUTHENTICATION_MODE
value: "none"
```
the config is not set in the …
-
**Describe the bug**
When tls enabled on gateway for [secure client communication](https://docs.camunda.io/docs/next/self-managed/zeebe-deployment/security/secure-client-communication/), readiness …