-
Notifications
You must be signed in to change notification settings - Fork 222
Closed
Labels
component:self-managedDocs and issues related to Camunda Platform 8 Self-ManagedDocs and issues related to Camunda Platform 8 Self-ManagedsupportIssues related to support ticketsIssues related to support tickets
Description
The customer in the support ticket learned unexpectedly that our Zeebe Brokers need to have the TLS options configured, which was unintuitive to the customer because their expectation was that the zeebe gateway would be handling these sorts of network requests. Lets add a mention on the following documentation page
and lets adjust the code-snippets here:
https://github.com/camunda/camunda-deployment-references/tree/main/aws/rosa-hcp/camunda-versions/8.6/procedure/install/helm-values
to include these extra environment variables necessary.
- name: ZEEBE_BROKER_NETWORK_SECURITY_ENABLED
value: "true"
- name: ZEEBE_BROKER_NETWORK_SECURITY_CERTIFICATECHAINPATH
value: "/usr/local/zeebe/config/tls.crt"
- name: ZEEBE_BROKER_NETWORK_SECURITY_PRIVATEKEYPATH
value: "/usr/local/zeebe/config/tls.key"
and necessary volumes+volumeMounts to support those settings.
Metadata
Metadata
Assignees
Labels
component:self-managedDocs and issues related to Camunda Platform 8 Self-ManagedDocs and issues related to Camunda Platform 8 Self-ManagedsupportIssues related to support ticketsIssues related to support tickets