[ISSUE] Cannot start a self managed cluster with latest release due to java.nio.file.AccessDeniedException: /usr/local/zeebe/data/.topology.meta
#2436
Labels
kind/issue
Unidentified issue, it could be a bug, misconfig, or anything in between
Describe the issue:
I'm trying to configure a Self Managed cluster using kubernetes, following the instructions at https://docs.camunda.io/docs/self-managed/setup/install.
When running
where
camunda-platform-core-kind-values.yaml
is defined as:the cluster is not able to start due to
camunda-platform-zeebe-master
failures:I also tried using latest camunda 8 helm charts following the guide:
but the cluster failes due to elasticsearch write/lock issues.
Actual behavior:
Expected behavior:
How to reproduce:
minikube start -p camunda8 --nodes 3
minikube profile camunda8
alias kubectl="minikube kubectl --"
Logs:
kubernetes cluster dashboard:
minikube status:
nodes:
kubectl cluster-info dump:
dump.txt
Environment:
The text was updated successfully, but these errors were encountered: